Catch up changelog with entries for July 20 - August 6 - #160
Merged
Conversation
zoltan-baba
approved these changes
Aug 10, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Retroactive changelog catch-up for @zoltanb's review — draft on purpose, since the changelog is your manually invoked skill. Nothing here is merged until you say so.
Scope
The last entry was dated 2026-07-14, but you ran the changelog yourself in #125 (merged 17 July). Everything merged before that run was your curation call, so this covers PRs merged after 2026-07-17 only: 22 PRs, 9 entries.
Entries added (9)
A new
## 2026 Augustsection was added above## 2026 July; July entries were inserted newest-first above the 07-14 entry.Skipped (13), with reasons
/ci(link changes only).bitrise.secrets.yml, dropped an incorrect$GOPATH/binprerequisite, replaced a removed Android Sign input). No new capability, so they fall under "corrections with no new information" — but they're the closest calls in the batch.Two things worth your eye
Every link in the new entries was verified against production — one draft slug was wrong (
workspace-collaborationsits undercollaboration-and-permissions-in-workspaces) and was corrected before committing.