Is gix no longer keeping a CHANGELOG.md?
#2362
-
|
The one in Just looking to see what the breaking changes are. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
This looks unintended, and like it affects some other gitoxide crates too, as seen in #2346 (comment). I think this discussion could be made into an issue, but I'll wait for @Byron. As a workaround, the changelogs for |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, it didn't auto-close the discussion with the creation of the related issue. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, my impression is that there's an intentional asymmetry between converting issues to discussions and creating issues from discussions. The former is meant mainly for the situation where something shouldn't be an issue at all but should be a discussion, while the latter is for when something should be an issue but where it may or may not make sense for a parallel discussion to remain open (the discussion may be about something broader in which the issue arose, or the discussion may be useful for the development of workarounds that developers find excessively noisy for the issue--though I think workarounds are more often useful in issues, where people will look for them). |
Beta Was this translation helpful? Give feedback.
This looks unintended, and like it affects some other gitoxide crates too, as seen in #2346 (comment). I think this discussion could be made into an issue, but I'll wait for @Byron.
As a workaround, the changelogs for
gixcan be read in the GitHub releases, at URLs that start withhttps://github.com/GitoxideLabs/gitoxide/releases/tag/gix-vfollowed by the version number. So https://github.com/GitoxideLabs/gitoxide/releases/tag/gix-v0.77.0 shows the changelog for 0.77.0. I definitely don't think we mean have that as the only place, though.