Skip to content

docs: add release please version range #201

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 23, 2024
Merged

docs: add release please version range #201

merged 2 commits into from
Jan 23, 2024

Conversation

beeme1mr
Copy link
Member

This PR

  • adds release please version range

Notes

This should work fine as long as the spec version is never the same as the release. Unfortunately, I had to include both tags because otherwise it introduces formatting issues.

@beeme1mr beeme1mr requested a review from a team as a code owner January 23, 2024 16:40
Copy link
Member

@askpt askpt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can put the release version only affecting the img shields for the version and not the spec. Makes sense?

Signed-off-by: Michael Beemer <[email protected]>
@beeme1mr beeme1mr merged commit aa35e25 into main Jan 23, 2024
arttonoyan pushed a commit to arttonoyan/dotnet-sdk that referenced this pull request Nov 17, 2024
Signed-off-by: Michael Beemer <[email protected]>
Signed-off-by: Artyom Tonoyan <[email protected]>
@askpt askpt deleted the fix-release-please branch February 28, 2025 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants