Skip to content

fix(release): align package version with v0.2.0 - #5

Merged
fffonion merged 1 commit into
masterfrom
subagent/ngx-ci-fix-20261117-872bc03e
Nov 16, 2026
Merged

fffonion merged 1 commit into
masterfrom
subagent/ngx-ci-fix-20261117-872bc03e

Conversation

@fffonion

Copy link
Copy Markdown
Contributor

Summary

  • Set the root crate and Cargo.lock package version to 0.2.0.
  • Align packaging expectations, public documentation and the ngx RustScript metadata host (2000) with that version. Keep the release workflow validation unchanged.

Failure and limitation

  • Release run 43889946904 failed in Build and publish linux-amd64 packages / Validate tag and package version: tag version 0.2.0 does not match Cargo.toml 0.1.0.
  • Root cause: the existing v0.2.0 tag points at a commit whose Cargo.toml still declares 0.1.0. The workflow checks out the tag, so merging this PR cannot change that existing tag snapshot. Only a future v0.2.0 tag pointing at a commit containing this change would pass this version check; handling the already existing tag requires separate release coordination.

Verification

  • cargo metadata --format-version 1 --no-deps --locked --offline: root package 0.2.0.
  • cargo check --locked --offline --lib: passed with configured official NGINX 1.31.4 headers.
  • cargo test --locked --offline --test ngx_meta compile_time_config_metadata_is_owned_and_truthful -- --test-threads=1: 1 passed.
  • python3 tests/test_release_packaging.py: 5 passed; the new version/lockfile test failed on the original 0.1.0 manifest before the fix.
  • python3 scripts/check_docs_links.py: 353 links checked.
  • cargo fmt --all -- --check and git diff --check: passed.
  • An NGINX executable/module integration build was not run; only the configured headers were needed for the focused Rust checks.

Synchronize the root crate, lockfile, packaging fixtures and host metadata so version validation and generated artifacts agree.
@fffonion
fffonion merged commit 9206523 into master Nov 16, 2026
1 check passed
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.

1 participant