Repository navigation
release: 0.43.1 #64
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
release: 0.43.1 #64
Changes from all commits
Commits
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,3 @@ | ||
| { | ||
| ".": "0.43.0" | ||
| ".": "0.43.1" | ||
| } |
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 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 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
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.
🟡 (optional) Customers installing 0.43.1 will send
X-Stainless-Package-Version: 0.43.0on every request, whileUser-Agentsays 0.43.1. The release bumpsVERSIONhere, but src/Client.php:120 hard-codes '0.43.0'. That file is not in release-please'sextra-files, so the tagged code ships with the old version. Fix: in the SDK configuration, have the generator build that header fromVERSION, asUser-Agentalready does. Or emit x-release-please markers there and list src/Client.php inextra-filesin a generated commit. Every release PR then bumps every version string. Don't hand-edit either file.Why this was flagged
src/Client.php:118 builds
User-Agentfrom theVERSIONconstant, which this PR sets to '0.43.1' at src/Version.php:8. src/Client.php:120 sets 'X-Stainless-Package-Version' => '0.43.0' as a literal. release-please-config.jsonextra-fileslists only README.md and src/Version.php, so this release PR leaves the literal alone. Once the PR merges, the published v0.43.1 package sends conflicting version headers on every request, and server-side analytics or debugging that keys on the package-version header files 0.43.1 traffic under 0.43.0. The literal is only fixed after the release, by a laterci(sdk): sync generated files after the releasecommit (b8d2bae changed '0.42.0' to '0.43.0' after 0.43.0 shipped). That sync never reaches the tagged code, so each release ships the previous version, as 0.43.0 did. The PR task asks that version strings match everywhere, and this one does not.Verification: nit. Trigger: every request from the published v0.43.1 package. This PR sets VERSION to
'0.43.1'at src/Version.php:8, but src/Client.php:120 is the literal'X-Stainless-Package-Version' => '0.43.0',. Client.php has no markers, so release-please does not rewrite the literal. On the base commit both values are 0.43.0 and agree.