Skip to content
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.

Sign up for GitHub

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

Add 1.7.1 and v1.6.5 to the Changelog #4347

Merged
merged 5 commits into from
Jul 27, 2023
Merged

Add 1.7.1 and v1.6.5 to the Changelog #4347

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6f13e2a
Add v1.7.1 to the changelog
amartinezfayo Jul 19, 2023
9da5f65
Address comments. Update target release date
amartinezfayo Jul 21, 2023
bb94012
Add #4352 as part of the Changelog
amartinezfayo Jul 26, 2023
75966b0
Add missing space
amartinezfayo Jul 26, 2023
c74728b
Add 1.6.5 release
amartinezfayo Jul 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,23 @@
# Changelog

## [1.7.1] - 2023-07-20

### Added

- x509pop node attestor emits a new selector with the leaf certificate serial number (#4216)
- HTTPS server in the OIDC Discovery Provider can now be configured to use a certificate file (#4190)
- Option to log source information in server and agent logs (#4246)

### Changed

- Improvement in entry lookup logic when fetching JWT-SVIDs (#4211)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dunno if this is worth mentioning since it is more or less just a code maintenance improvement?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it translates into a meaningful perf benefit, we could say something like "reduced CPU/memory usage when fetching JWT-SVIDs"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will probably not be a noticeable perf improvement in most cases. I'm now more inclined to remove this.

- Agent now has an exponential backoff strategy when syncing with the server (#4279)

### Fixed

- Bug distinguishing audience sets in the agent's JWT-SVID cache (#4309)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably be talking about user impact here, e.g.

- SPIRE Agent cache bug resulting in workloads receiving JWT-SVIDs with incomplete audience set

- The `spire-server agent show` command to properly show the "Can re-attest" attribute (#4288)

## [1.7.0] - 2023-06-14

### Added
Expand Down