chore(release): bump workspace version to 0.1.10
Release / build (x86_64-unknown-linux-gnu) (push) Failing after 6s
Release / build (aarch64-apple-darwin) (push) Canceled after 0s
Release / build (aarch64-unknown-linux-gnu) (push) Canceled after 0s
Release / build (x86_64-apple-darwin) (push) Canceled after 0s
Release / build (x86_64-pc-windows-msvc) (push) Canceled after 0s
Release / publish GitHub Release (push) Canceled after 0s
Release / build (x86_64-unknown-linux-gnu) (push) Failing after 6s
Release / build (aarch64-apple-darwin) (push) Canceled after 0s
Release / build (aarch64-unknown-linux-gnu) (push) Canceled after 0s
Release / build (x86_64-apple-darwin) (push) Canceled after 0s
Release / build (x86_64-pc-windows-msvc) (push) Canceled after 0s
Release / publish GitHub Release (push) Canceled after 0s
All 62 crates inherit `workspace.package.version`, so the single edit plus the refreshed lockfile carries the release. The `v0.1.10` tag is what triggers the build; release.yml gates the tag against this value. Also records the shared-SSRF-policy invariant in AGENTS.md, so a future port does not reintroduce a second copy. The zero-egress entry is compressed by the same number of lines to keep the file at 500.
This commit is contained in:
1 parent
bac8470c80
commit
11c3ca9803
3 files changed
+71
-71
No files matched your search
+1
-1
@@ -76,7 +76,7 @@ members = [
|
||||
]
|
||||
|
||||
[workspace.package]
|
||||
version = "0.1.9"
|
||||
version = "0.1.10"
|
||||
edition = "2024"
|
||||
license = "Apache-2.0"
|
||||
|
||||
|
||||
Reference in new issue
Block a user