-
Notifications
You must be signed in to change notification settings - Fork 14
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
chore: release v0.5.0 #38
base: main
Are you sure you want to change the base?
Conversation
b230f13
to
f77bf23
Compare
1a86b6a
to
7ea2def
Compare
7ea2def
to
ee42115
Compare
e66d997
to
9e05b9e
Compare
|
||
### 📚 Documentation | ||
|
||
- Add doc comments for tproxy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jwhb Hmm, could it be that feat:
commits are not getting picked up git-cliff at the moment? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is strange about this is that running git-cliff
locally actually generates the changelog as you would expect... Not sure why the GitHub Action is generated an incorrect version, as it is clearly picking up that there has been at least one feat:
commit that implies bumping the crate's minor version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, seems to me as if the dependency updates are also not picked up by the GitHub Action anymore 🤔
9e05b9e
to
2bd63f0
Compare
2bd63f0
to
10c6f19
Compare
5488bbd
to
2278750
Compare
2278750
to
da815ab
Compare
🤖 New release
nftables
: 0.4.1 -> 0.5.0Changelog
This PR was generated with release-plz.