Bump fallback Version to 0.11.0 - #144
Merged
Merged
Conversation
There was a problem hiding this comment.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Auto-approved: Bumps the fallback version in Directory.Build.props to 0.11.0 to align with the upcoming release for local builds.
Re-trigger cubic
Approval not submitted
This repository is configured to approve as @klotty, but that approval identity is unavailable.
Reconnect or verify the approval identity in repository settings.
cubic left this as a normal review comment instead of falling back to a Cubic App approval.
gabrielmfern
approved these changes
Aug 21, 2026
This was referenced Aug 21, 2026
This was referenced Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Directory.Build.propsstill had the fallback<Version>at0.10.0, behind the release about to be cut (v0.11.0, covering feat: add EmailShareAsync method #142 EmailShareAsync and feat(api-keys): add ApiKeyUpdateAsync for PATCH /api-keys/:id #143 api-keys update). Localdotnet build/dotnet packruns (outside CI) would pick up this stale version since it's not overridden by a tag-derived-p:Version=likecicd/release.shdoes for actual releases.0.11.0to match the upcoming release, following the repo's existing convention (see Bump fallback Version to 0.9.0 #141, Bump fallback Version to 0.6.0 #131).Test plan
Directory.Build.props)dotnet build -c Releasesucceeds with only the two pre-existing unrelated warningsrelease.shderives version from the git tag via-p:Version=, so this change doesn't affect the release pipeline itselfSummary by cubic
Aligns the fallback package version with the upcoming release by updating Directory.Build.props from 0.10.0 to 0.11.0. Previously, local dotnet builds/packs defaulted to 0.10.0; now they default to 0.11.0. The release pipeline remains unchanged since it injects the version via -p:Version from the tag.
Written for commit c3e5f00. Summary will update on new commits.