Skip to content

Tracking PR for v0.14.0 relese#1603

Draft
bobbinth wants to merge 106 commits intomainfrom
next
Draft

Tracking PR for v0.14.0 relese#1603
bobbinth wants to merge 106 commits intomainfrom
next

Conversation

@bobbinth
Copy link
Contributor

This is a tracking PR for v0.14.0 release.

This removes a few levels of path nesting.
* chore: ntx-builder followups

* review: improve span formatting

Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>

---------

Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>
* chore: bump workspace version to 0.14.0-alpha.1

Pin protocol dependencies to published crate versions and update all
workspace crate versions to =0.14.0-alpha.1.

https://claude.ai/code/session_017j1F8cwRXFnWyjzzwN9d4k

* ci: support publishing from non-main branches

Use github.event.release.target_commitish to dynamically determine
which branch to checkout and verify against, instead of hardcoding
main. This enables releasing alpha versions from the next branch.

https://claude.ai/code/session_017j1F8cwRXFnWyjzzwN9d4k

* feat: use StorageMapEntry instead of Word

* feat: use StorageMapEntry in tests

* chore: simplify Digest<>StorageMapEntry conv

* chore: rename key -> key_hash

* Apply suggestions from code review

Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>

* chore: simplify crate publishing step

* chore: bring msvr check from main

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>
juan518munoz and others added 2 commits March 4, 2026 23:04
* fix: preemptive evaluation

* chore: linting

* chore: bump path version

* fix: bump crate versions as well

* chore: fix linting due to rust version
mmagician and others added 5 commits March 5, 2026 12:25
* chore: test network accounts get details

* chore: network accounts should make it to genesis state

* Apply suggestion from @mmagician

* clippy
* fix: lenient pre-release matching in accept header validation

Match on the pre-release label (e.g. "alpha") but ignore the numeric
suffix, so a server at 0.14.0-alpha.3 accepts clients at alpha.1,
alpha.2, etc. This allows client and node to evolve independently
within the same pre-release phase.

- Stable and pre-release remain incompatible
- Different labels (alpha vs beta) remain incompatible
- Patch versions remain flexible (0.14.0 and 0.14.1 both accepted)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* chore: add changelog entry for lenient pre-release matching

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix: reject different patch versions for pre-release

Pre-release versions now require exact patch match in addition to
matching the pre-release label. Patch flexibility only applies to
stable versions. For example, a 0.14.0-alpha.3 server rejects
0.14.1-alpha.1 but a stable 0.14.0 server still accepts 0.14.1.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* lint

---------

Co-authored-by: Claude (Opus) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.