-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Release tags in git #2229
Comments
Our GitHub tags use version 2. We have no good way of publishing our releases/tags for version 3 because it's modular. It's fixed in this version: https://github.com/aws/aws-sdk-ruby/blob/master/gems/aws-sdk-core/CHANGELOG.md#3542-2019-06-03 |
I see. Is there a good way for me to tell what commit was in a particular release? Reading through changelogs seems rough. Also is there a way to know what git revision is equivalent to a particular release? Thanks for your time! |
For V3, there's no good way to do so. In the commit there will generally be an "unreleased" changelog entry. If it's marked as an "issue" then it will add a patch version bump, if it's marked as a "feature" it will be a minor version bump. I suppose you could look at the previous entry and determine that. |
@mullermp ok, thanks for the info! 🙇🏻♀️ |
No problem. If you have any idea on how to best tag those, I'm open to suggestions. We could tag |
Re-opening as a feature request to do git release tagging based around dates. |
Hi,
I'm trying to find what version shipped with d98d94c, but I found that none of the v3.X tags have been pushed to GitHub. Could someone push the tags please?
Thanks!
The text was updated successfully, but these errors were encountered: