-
Notifications
You must be signed in to change notification settings - Fork 31
Add changelog entry for 0.5.5 #974
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
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,21 @@ | ||
| authd (0.5.6) questing; urgency=medium | ||
|
|
||
| * New launchpad upload | ||
|
|
||
| -- Adrian Dombeck <[email protected]> Wed, 18 Jun 2025 16:05:23 +0200 | ||
|
|
||
| authd (0.5.5) questing; urgency=medium | ||
|
|
||
| * Fix race with accounts service which could result in authd users not being | ||
| listed in the GDM login screen. | ||
| * When authenticating on the command-line, show a message that explains that | ||
| the escape key can be used to go back. | ||
| * Improve log message. | ||
| * Update Go dependencies: | ||
| - toolchain go1.23.10 | ||
|
|
||
| -- <[email protected]> Tue, 17 Jun 2025 19:42:04 +0200 | ||
|
|
||
| authd (0.5.4) questing; urgency=medium | ||
|
|
||
| * CVE-2025-5689: Fix new users logging in via SSH being part of the root group | ||
|
|
||
Oops, something went wrong.
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.
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.
Mh, this was needed for?
I would like that we get a way to avoid to do uploads of invalid tags or ubuntu uploads though, maybe using your local fork and more
~preuploads?Maybe specify it better in changelog.
However... Please also use
-v0.5.4when generating the*.changesfile to upload to the stable PPA :)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.
I did
v0.5.5~pre1for the testing. when I finalized the release, I removed that suffix and uploaded to launchpad to build the 0.5.5 release, and only when that was uploaded to the edge PPA I noticed in the diff that it contains unexpected changes from mainThere 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.
ah, too late, 0.5.6 is already building on launchpad with -v0.5.5 :/
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.
So we have two options, add another 0.5.7 entry or release with the .changes files with the diff between 0.5.6 and 0.5.5 (where the latter contains the changes from main)
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.
Not a big deal. But next time remember in order to ensure that the changes we generate is meaningful, so ignoring the minor updates
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.
Yeah sure, makes sense, I just didn't think about it
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.
Oh, I actually see that's still in edge only, no?
So if that is the case, you can just regenerate the changes file from that same source when uploading to stable no?
There's no need to do it through the lp UI (and sources are still the same, so no risk)
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.
Ok, will do that now