Prepare release 0.6.6 #53
Merged
Conversation
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
This release has no functional changes. It is intended to be the first release where upload of the traceability report works. It is not great to make a new release simply to trigger the upload, but I would like to avoid re-building a new git revision (d28705a) with the existing 0.6.5 tag. This would mean we have a traceability report for a build which does not exactly match the revision uploaded to pypi.org, even if there no functional changes.
karthikmswamy
approved these changes
Jul 21, 2020
Contributor
karthikmswamy
left a comment
karthikmswamy
left a comment
There was a problem hiding this comment.
Thanks! Now I see what you mean by no functional changes :)
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.
This release has no functional changes. It is intended to be the
first release where upload of the traceability report works.
It is not great to make a new release simply to trigger the upload,
but I would like to avoid re-building a new git revision
(d28705a) with the existing 0.6.5 tag.
This would mean we have a traceability report for a build which does not
exactly match the revision uploaded to pypi.org, even if there no
functional changes.