chore[notask]: backmerge release sdk 0.9.1#1726
Merged
opaninakuffo merged 1 commit intoApr 23, 2026
Merged
Conversation
Victor-Rodzko
approved these changes
Apr 23, 2026
NamelsKing
approved these changes
Apr 23, 2026
Contributor
Author
|
review |
Contributor
Tier-based Approval Status |
This was referenced May 1, 2026
NamelsKing
added a commit
that referenced
this pull request
May 4, 2026
* QVAC-18184 chore[notask|skiplog]: backmerge release sdk 0.9.2 Brings the 0.9.2 release artifacts back into main now that @qvac/sdk@0.9.2 has been published to npm (`latest` dist-tag, 2026-05-01 10:09 UTC). - Bump packages/sdk/package.json: 0.9.1 -> 0.9.2 - Add packages/sdk/changelog/0.9.2/CHANGELOG.md and CHANGELOG_LLM.md - Prepend 0.9.2 entry to aggregated packages/sdk/CHANGELOG.md Hotfix content (z.xor -> z.union, zod floor bump) is the cherry-pick of #1790 that already landed on main, so no source changes here. Dependencies in package.json are intentionally NOT brought over from the release branch — main has progressed past 0.9.1 on several internal packages (e.g. @qvac/llm-llamacpp 0.14.4 -> 0.17.1, @qvac/translation-nmtcpp 0.6.10 -> 2.0.1, react-native-bare-kit 0.11.5 -> 0.12.3) and a blind merge would regress them. Only the version field is changed, matching the 0.9.1 backmerge precedent (#1726). * chore[skiplog]: drop package.json version bump from backmerge to avoid conflict with 0.10.0 PR PR #1865 (the 0.10.0 release) is open against main and bumps packages/sdk/package.json version 0.9.1 -> 0.10.0. This backmerge was bumping the same line 0.9.1 -> 0.9.2, so whichever lands second hits a conflict on that single line. Since main is moving to 0.10.0 directly (the 0.9.2 hotfix is a separate release line), drop the package.json change from this backmerge and let #1865 own the version bump. Main's package.json will briefly say 0.9.1 while CHANGELOG.md lists 0.9.2 as the latest shipped version, but that's transient — #1865 overwrites it to 0.10.0 anyway. Keep the changelog artifacts (changelog/0.9.2/ folder + the prepended ## [0.9.2] entry in aggregated CHANGELOG.md) so main retains a record of the 0.9.2 release in its history. --------- Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>
tamer-hassan-tether
pushed a commit
that referenced
this pull request
May 5, 2026
* QVAC-18184 chore[notask|skiplog]: backmerge release sdk 0.9.2 Brings the 0.9.2 release artifacts back into main now that @qvac/sdk@0.9.2 has been published to npm (`latest` dist-tag, 2026-05-01 10:09 UTC). - Bump packages/sdk/package.json: 0.9.1 -> 0.9.2 - Add packages/sdk/changelog/0.9.2/CHANGELOG.md and CHANGELOG_LLM.md - Prepend 0.9.2 entry to aggregated packages/sdk/CHANGELOG.md Hotfix content (z.xor -> z.union, zod floor bump) is the cherry-pick of #1790 that already landed on main, so no source changes here. Dependencies in package.json are intentionally NOT brought over from the release branch — main has progressed past 0.9.1 on several internal packages (e.g. @qvac/llm-llamacpp 0.14.4 -> 0.17.1, @qvac/translation-nmtcpp 0.6.10 -> 2.0.1, react-native-bare-kit 0.11.5 -> 0.12.3) and a blind merge would regress them. Only the version field is changed, matching the 0.9.1 backmerge precedent (#1726). * chore[skiplog]: drop package.json version bump from backmerge to avoid conflict with 0.10.0 PR PR #1865 (the 0.10.0 release) is open against main and bumps packages/sdk/package.json version 0.9.1 -> 0.10.0. This backmerge was bumping the same line 0.9.1 -> 0.9.2, so whichever lands second hits a conflict on that single line. Since main is moving to 0.10.0 directly (the 0.9.2 hotfix is a separate release line), drop the package.json change from this backmerge and let #1865 own the version bump. Main's package.json will briefly say 0.9.1 while CHANGELOG.md lists 0.9.2 as the latest shipped version, but that's transient — #1865 overwrites it to 0.10.0 anyway. Keep the changelog artifacts (changelog/0.9.2/ folder + the prepended ## [0.9.2] entry in aggregated CHANGELOG.md) so main retains a record of the 0.9.2 release in its history. --------- Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>
Proletter
pushed a commit
that referenced
this pull request
May 24, 2026
Proletter
pushed a commit
that referenced
this pull request
May 24, 2026
* QVAC-18184 chore[notask|skiplog]: backmerge release sdk 0.9.2 Brings the 0.9.2 release artifacts back into main now that @qvac/sdk@0.9.2 has been published to npm (`latest` dist-tag, 2026-05-01 10:09 UTC). - Bump packages/sdk/package.json: 0.9.1 -> 0.9.2 - Add packages/sdk/changelog/0.9.2/CHANGELOG.md and CHANGELOG_LLM.md - Prepend 0.9.2 entry to aggregated packages/sdk/CHANGELOG.md Hotfix content (z.xor -> z.union, zod floor bump) is the cherry-pick of #1790 that already landed on main, so no source changes here. Dependencies in package.json are intentionally NOT brought over from the release branch — main has progressed past 0.9.1 on several internal packages (e.g. @qvac/llm-llamacpp 0.14.4 -> 0.17.1, @qvac/translation-nmtcpp 0.6.10 -> 2.0.1, react-native-bare-kit 0.11.5 -> 0.12.3) and a blind merge would regress them. Only the version field is changed, matching the 0.9.1 backmerge precedent (#1726). * chore[skiplog]: drop package.json version bump from backmerge to avoid conflict with 0.10.0 PR PR #1865 (the 0.10.0 release) is open against main and bumps packages/sdk/package.json version 0.9.1 -> 0.10.0. This backmerge was bumping the same line 0.9.1 -> 0.9.2, so whichever lands second hits a conflict on that single line. Since main is moving to 0.10.0 directly (the 0.9.2 hotfix is a separate release line), drop the package.json change from this backmerge and let #1865 own the version bump. Main's package.json will briefly say 0.9.1 while CHANGELOG.md lists 0.9.2 as the latest shipped version, but that's transient — #1865 overwrites it to 0.10.0 anyway. Keep the changelog artifacts (changelog/0.9.2/ folder + the prepended ## [0.9.2] entry in aggregated CHANGELOG.md) so main retains a record of the 0.9.2 release in its history. --------- Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>
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
3 participants
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.
🎯 What problem does this PR solve?
@qvac/sdkto0.9.1to validate infra workflow changes.📝 How does it solve it?
packages/sdk/package.jsonfrom0.9.0→0.9.1.packages/sdk/changelog/0.9.1/(CHANGELOG.md+CHANGELOG_LLM.md) and re-aggregate rootpackages/sdk/CHANGELOG.md.