- Notifications
You must be signed in to change notification settings - Fork744
Update using-latest-daily.md#7692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (1)
docs/using-latest-daily.md:49
- There is an inconsistency in the command examples: the first example omits the 'dotnet new install' command and '--force' flag, while the second example includes them. Consider unifying both examples to improve clarity.
> Release branches are a little different. For example, for the latest build from `release/X.X` branch change the above to be `Aspire.ProjectTemplates::X.X.*-*`. For example, if you want to use the latest build from the `release/9.2` branch, change the above to be `dotnet new install Aspire.ProjectTemplates::9.2.*-* --force`Uh oh!
There was an error while loading.Please reload this page.
| ``` | ||
| >[!TIP] | ||
| >Ifyou want to use the latest build from the`release/9.0-rc1` branch, change the above to be`dotnet new install Aspire.ProjectTemplates::9.0.0-rc.1.* --force` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
@wtgodbe was this correct? there's a period between rc and 1 that wasn't in 9.0-rc1. I guess , whatever
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Are you saying there was a time when we were versioning packages "9.0.0-rc-{suffix}"? That doesn't sound right
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I'm saying the deleted line contains both "rc1" and "rc.1"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Oh, that's fine. The branch would be named rc1, and the packages would be versioned rc.1. That's typical.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
that's fine but it means we need to document the feed for each rc, since they can't follow the obvious pattern.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Maybe I'm confused - it looks to me like the language here describes how to specify the package version, not the feed. Each release/9* branch will publish to the same feed (dotnet9) up until the point that we stabilize - the same is true for RC branches
Uh oh!
There was an error while loading.Please reload this page.
5126607 intomainUh oh!
There was an error while loading.Please reload this page.
No description provided.