[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACYQ2B1Z1DCE9DSS064R8V":3,"skill-same:01M6ACYQ2B1Z1DCE9DSS064R8V":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6ACYQ2B1Z1DCE9DSS064R8V","fory-release",null,"Stage or verify an Apache Fory release candidate and prepare GitHub release notes. Use GitHub Actions by default for ATR source staging and Nexus JVM staging; use the retained local manual workflow only when the user explicitly requests manual publishing.","apache\u002Ffory","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACYG841PGN6KSQGHBNJTNF",4582,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-release\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,9],"release","fory release","fory","publishing","manual","for","github release","source","jvm","notes","candidate","when","release notes","only","github actions","local","default","actions","workflow","2026-11-10 10:12:30",false,"---\nname: fory-release\ndescription: Stage or verify an Apache Fory release candidate and prepare GitHub release notes. Use GitHub Actions by default for ATR source staging and Nexus JVM staging; use the retained local manual workflow only when the user explicitly requests manual publishing.\n---\n\n# Apache Fory Release\n\nUse `.github\u002Fworkflows\u002Fstage-release-candidate.yml` for source and JVM staging\nunless the user explicitly asks for a manual release. The workflow uses\n`ci\u002Frelease.py`; do not reproduce its source-build, JVM-publication, Nexus\nclosure, or artifact-verification logic in shell commands. Do not add unrelated\ntest runs.\n\nRelease automation, CI, and artifact-compliance fixes belong in PRs targeting\n`apache\u002Fmain`. Merge those fixes before preparing the candidate. Keep the\nversion-preparation branch local and push only the immutable RC tag; do not\npush a `releases-*` branch or target it with repair PRs unless the release\nmanager explicitly requests that separate branch workflow.\n\n## CI signing and staging prerequisites\n\nThe workflow runs only in `apache\u002Ffory` and uses these Infra-provisioned GitHub\nActions secrets:\n\n| Secret                      | Purpose                                                     |\n| --------------------------- | ----------------------------------------------------------- |\n| `FORY_GPG_SECRET_KEY`       | Import the Infra-managed CI signing key in each signing job |\n| `NEXUS_STAGE_DEPLOYER_USER` | Authenticate Java\u002FKotlin and Scala Nexus staging            |\n| `NEXUS_STAGE_DEPLOYER_PW`   | Authenticate Java\u002FKotlin and Scala Nexus staging            |\n\nSource staging uses ATR with GitHub OIDC, not SVN credentials. Do not add a\npersonal signing key, a GPG passphrase secret, or SVN credentials to this flow.\n\nSource packaging requires Syft 1.57.0. CI installs this pinned version; install\nthe same version on the trusted verification machine and put `syft` on `PATH`\n(or set `SYFT` to its executable path). The build emits a signed CycloneDX 1.6\nSBOM beside the source archive, with its own SHA-512 checksum. It inventories\nthe manifests and lock files included in the archive; it is not a complete\nresolved dependency inventory for every runtime's binaries. Dependency\nenrichment is disabled and the source commit supplies the timestamp so the\nSBOM can be compared byte-for-byte during verification.\n\nThe source archive includes `.rat-excludes` for machine-readable metadata,\nbundled license texts, and specifically attributed third-party files. Keep\nthird-party notices intact. The matching lightweight-check exclusions are in\n`.asf.yaml` under `project.policy.source_excludes_lightweight`. ASF synchronizes\nthat policy from the default branch. After merging policy changes to\n`apache\u002Fmain`, confirm the exact patterns are active in ATR before staging.\nDo not disable either license check or add broad source-directory exclusions.\n\nThe Nexus account must have staging access to the `org.apache.fory` profile.\nProvisioning the shared CI credentials alone does not grant access to this\nproject. `stage_jvm` checks profile access before building or uploading artifacts;\nif it is missing, ask Infra to grant Fory staging access to the provisioned CI\naccount. Do not replace the CI credentials with a personal account.\n\nBefore the first CI release, or after a signing-key rotation:\n\n- Obtain the CI public key and its full primary fingerprint from Infra's message\n  to the project's private mailing list. Confirm that this public key is present\n  in the published [Fory KEYS](https:\u002F\u002Fdownloads.apache.org\u002Ffory\u002FKEYS). If it is\n  absent, arrange publication of the public key before staging a candidate.\n  Keep private key material and revocation certificates out of the repository.\n- Set `gpg_fingerprint` to that independently confirmed CI key fingerprint for\n  local verification and the vote email. Do not reuse a personal signing\n  fingerprint from an earlier manual release or trust a CI log alone.\n- Merge the staging workflow to the default branch before dispatching it, and\n  create the RC from a commit that contains the workflow. Do not move an old RC\n  tag to make the workflow available.\n\nSecret provisioning and ordinary PR checks do not prove that signing, ATR\nupload, or Nexus staging works. The first authorized CI staging run must succeed,\nand its artifacts must pass the trusted-hardware verification below before voting.\n\n## Required Inputs\n\nCollect these values before starting:\n\n- `release_version`: final version without `v` or an RC suffix, such as `1.7.0`.\n- `rc`: RC suffix, such as `rc3`.\n- `previous_version`: previous release tag version, such as `1.6.1`.\n- Release discussion URL, if already known. If it is not supplied, find the\n  exact release thread in the Fory development-list archive as described below.\n\nDerive the release values:\n\n```bash\nrelease_branch=\"releases-${release_version}\"\nrc_tag=\"v${release_version}-${rc}\"\nrelease_candidate_url=\"https:\u002F\u002Freleases.apache.org\u002Fdownload\u002Fpath\u002Ffory\u002F${release_version}\"\n```\n\n### Find the release discussion\n\nIf the release discussion URL was not supplied, search the\n[Fory development-list archive](https:\u002F\u002Flists.apache.org\u002Flist.html?dev@fory.apache.org)\nfor the exact release version and a `[DISCUSS]` subject. Use the deterministic\nhelper, which accepts exactly one root discussion thread:\n\n```bash\ndiscussion_url=\"$(\n  python3 .agents\u002Fskills\u002Ffory-release\u002Fscripts\u002Ffind_discussion.py \\\n    \"$release_version\"\n)\"\n```\n\nOpen the resulting URL and verify that its subject and body discuss the exact\n`release_version`. If the automated search finds zero or multiple roots, use\nthe archive UI to search the same exact version and `[DISCUSS]`; ask the release\nmanager only if the result remains absent or ambiguous. When a URL is supplied,\nopen and verify it instead of assuming it matches this release.\n\n## Default CI Workflow\n\n### 1. Create a clean local release branch\n\nRun from the repository root. Clean means no staged, modified, or untracked files.\n\n```bash\ntest -z \"$(git status --porcelain)\"\ntest \"$(git remote get-url apache)\" = \"git@github.com:apache\u002Ffory.git\"\ngit fetch apache main --tags\ngit switch -c \"$release_branch\" apache\u002Fmain\ntest -z \"$(git status --porcelain)\"\n```\n\nFor a new release branch, stop if the branch already exists or either cleanliness check fails. To resume an existing candidate, follow [Release retries](#release-retries) instead of recreating its branch or tag. Do not remove or hide user files to make the check pass.\n\n### 2. Bump the version\n\n```bash\npython3 ci\u002Frelease.py bump_version -version \"$release_version\" -l all\ngit diff --check\ngit status --short\n```\n\nReview the version diff. Use this command directly; do not substitute another version-bump workflow.\n\n### 3. Commit the release version\n\n```bash\ngit add -u\ngit commit -m \"prepare release for ${release_version}\"\ntest -z \"$(git status --porcelain)\"\nrelease_commit=\"$(git rev-parse HEAD)\"\n```\n\nStage only the version changes produced by the release script. Keep this\nversion-preparation commit local until the RC tag is pushed in the next step.\n\n### 4. Create and push the RC tag\n\nBefore creating a new RC tag, confirm that neither the local nor remote tag already exists. Never move, delete, or overwrite a published RC tag. Retrying a workflow for its existing tag does not create a new candidate; follow [Release retries](#release-retries).\n\n```bash\ntest -z \"$(git tag --list \"$rc_tag\")\"\ntest -z \"$(git ls-remote --tags apache \"refs\u002Ftags\u002F${rc_tag}\")\"\ntest \"$(git rev-parse HEAD)\" = \"$release_commit\"\ngit tag \"$rc_tag\" && git push apache \"$rc_tag\"\ntest \"$(git rev-parse \"${rc_tag}^{commit}\")\" = \"$release_commit\"\n```\n\nThe tag starts the ecosystem package-release workflows. A later infrastructure\nfailure does not by itself change the candidate; diagnose it using\n[Release retries](#release-retries).\n\n### 5. Stage source and JVM artifacts in CI\n\nDispatch the staging workflow on the immutable RC tag:\n\n```bash\ngh workflow run stage-release-candidate.yml \\\n  --repo apache\u002Ffory \\\n  --ref \"$rc_tag\" \\\n  -f source=true \\\n  -f jvm=true\n```\n\nRecord the exact workflow run ID and URL and wait for it with\n`gh run watch --exit-status`. Do not select a run only by commit SHA because a\nmain-branch run can share the same commit. The workflow stages the signed source\narchive to Apache Trusted Release through OIDC, publishes the JVM artifacts,\nand closes the Java\u002FKotlin and Scala Nexus repositories. It does not use SVN.\n\nFrom the successful run summary, record and open both distinct Nexus staging\nrepository IDs and the ATR candidate URL. Also record the reported Java runtime\nversion and vendor for the independent rebuild:\n\n```bash\njava_kotlin_staging_id=\"orgapachefory-...\"\nscala_staging_id=\"orgapachefory-...\"\njava_runtime_version=\"...\" # Complete java.runtime.version from JVM staging\njava_vendor=\"...\" # Exact java.vendor from JVM staging\ntest -n \"$java_kotlin_staging_id\"\ntest -n \"$scala_staging_id\"\ntest \"$java_kotlin_staging_id\" != \"$scala_staging_id\"\n```\n\nKeep both repositories closed during the vote. Do not promote them until the\nvote passes.\n\n### 6. Check the tag-triggered workflows\n\nInspect every workflow triggered by the tag. Filter by the tag rather than only\nby commit SHA so main-branch runs at the same commit are not mixed into the\nresult. By default, wait for every run and require successful conclusions:\n\n```bash\npython3 .agents\u002Fskills\u002Ffory-release\u002Fscripts\u002Fcheck_tag_workflows.py \\\n  --repo apache\u002Ffory \\\n  --tag \"$rc_tag\" \\\n  --commit \"$release_commit\" \\\n  --watch\n```\n\nThe helper re-queries by tag after waiting to catch later-created runs. A failed\nrun requires diagnosis, not an automatic RC increment. For a transient failure,\nrerun only the failed jobs with `gh run rerun \u003Crun-id> --repo apache\u002Ffory --failed`,\nthen run the helper again for the same tag and commit.\n\nIf the release manager explicitly waives workflow monitoring for a particular RC, run\nthe same command with `--allow-incomplete` instead of `--watch`, and record the\nsnapshot IDs, states, and reason. Do not cancel the remote workflows or report\nincomplete runs as successful.\n\n### 7. Verify all CI artifacts on trusted hardware\n\nDo not run this comparison in GitHub Actions. Use the independently confirmed\nInfra-managed CI key fingerprint from the prerequisites. Install the same JDK\ndistribution and complete runtime version recorded by JVM staging, including the\nbuild suffix, and set `JAVA_HOME` and `PATH` to it. Then run the repository\nverifier on a machine controlled by the release manager:\n\n```bash\n: \"${gpg_fingerprint:?missing CI signing-key fingerprint}\"\npython3 ci\u002Frelease.py verify_ci_artifacts \\\n  -v \"$release_version\" \\\n  --rc-tag \"$rc_tag\" \\\n  --java-kotlin-id \"$java_kotlin_staging_id\" \\\n  --scala-id \"$scala_staging_id\" \\\n  --gpg-fingerprint \"$gpg_fingerprint\" \\\n  --java-runtime-version \"$java_runtime_version\" \\\n  --java-vendor \"$java_vendor\" \\\n  --source-url \"$release_candidate_url\"\n```\n\nThe command checks out the exact RC commit in a temporary clone, rebuilds the\nsource archive, source SBOM, and complete JVM publication without signing or upload\ncredentials, verifies the staged signatures with the public key, and compares\nevery source, JAR, POM, source JAR, documentation JAR, and distribution file\nbyte-for-byte. Each JVM ecosystem is built once and may reuse the machine's\nnormal dependency caches; only source and build outputs are clean. It writes a\nMarkdown report under `dist\u002F`. Any mismatch or missing artifact blocks the vote.\nBefore downloading or rebuilding, the verifier requires an OpenJDK 25 runtime\nwhose `java.runtime.version` and `java.vendor` exactly match the supplied staging\nvalues. Matching only the Java major version is insufficient. The verifier also\nrequires the expected public key in `KEYS`;\nlocal personal keyrings are not used to satisfy this check.\nFailed verification retains the local rebuild and downloaded artifacts beside\nthe report for diagnosis; successful verification removes these temporary files.\nAfter a download failure, retry with `--rebuild-dir \u003Cretained-directory>` to\nreuse the completed unsigned build on the same machine without recompiling.\nThe completed rebuild must have a matching JDK record; a missing or different\nrecord requires a fresh build. The checkout must still match the RC commit and\nremain unchanged. Downloads,\nsignature checks, and every byte comparison run again; retained files are not\ndeleted in this mode.\nSource packaging uses a direct `git archive` of the RC tag without rewriting\n`LICENSE`, creating commits, or moving refs. Benchmark-specific attribution stays\nin `benchmarks\u002FLICENSE` and `benchmarks\u002FNOTICE` with the excluded benchmark sources.\n\n### 8. Draft the vote email\n\nLoad only the release-manager identity from `.local\u002Ffory-release.env` when\ndrafting the email. Never commit this ignored file or store release secrets in\nit.\n\n```bash\nrelease_config=\"$(git rev-parse --show-toplevel)\u002F.local\u002Ffory-release.env\"\ntest -f \"$release_config\"\n. \"$release_config\"\nrelease_manager_name=\"${FORY_RELEASE_MANAGER_NAME:?missing release manager name}\"\n```\n\nRead [the vote email template](assets\u002Fvote-email.txt) and produce a complete,\ncopyable email. Fill every placeholder from verified output, attach the\ntrusted-hardware report or link an existing public copy, and state that the vote\nremains open for at least 72 hours without specifying a closing date or time.\nDo not send the email unless requested.\n\n## Explicit Manual Workflow\n\nOnly when the user explicitly requests manual publishing, read and follow\n[the manual release workflow](references\u002Fmanual-release.md). Do not fall back\nto it automatically after a CI failure.\n\n## Verification-Only Requests\n\nFor an existing candidate, do not create another tag or staging repository.\nConfirm the exact tag, commit, source URL (ATR or manual SVN), both Nexus\nrepository IDs, and signing-key fingerprint from the vote. Check the tag workflows\nand run step 7 against those artifacts. Rebuild the unmodified RC checkout, not\nthe verifier's branch; never copy newer POMs or sources into the RC to force a\nmatch. Report any mismatch against the original candidate.\n\n## GitHub Release Title and Notes\n\nWhen authorized to create the final GitHub Release after the vote passes:\n\n- Set the title to the version tag alone, such as `v1.7.6`, not\n  `Apache Fory 1.7.6`. Use `--title \"v${release_version}\"` when creating it with\n  `gh release create`.\n- Put important features in a `## Highlights` section before the full change\n  list. Give each important feature its own named `###` subsection rather than\n  leaving it only as an entry in the change list. Explain what users can do with\n  it and include a concise example or documentation link where useful.\n- Describe only features included in that release; preserve the complete\n  change list after the highlights.\n\n## Release retries\n\nAn RC identifies the release content under review, not a CI attempt. Inspect the\nfailed step and its logs before deciding how to recover. Network timeouts,\ndependency-download failures, runner failures, and interrupted status checks do\nnot by themselves invalidate an unchanged candidate.\n\nWithout a substantive release change, keep the same release commit and RC tag\nand resume only the failed or incomplete steps. Preserve verified Maven staging\nrepositories and source artifacts; do not rebuild or republish successful\nartifacts merely because an unrelated CI job failed. Before retrying a push,\nupload, Nexus action, or SVN commit, inspect remote state because an interrupted\nrequest may already have succeeded. Use the Nexus reference's `--verify-only`\npath for repositories that are already closed.\n\nCreate a higher RC only when a substantive fix changes the release content,\nsuch as source, dependencies, build inputs, or packaging. Commit the actual fix\nbefore tagging the replacement; do not create an empty commit or a second RC\nat the same unchanged release commit just to retry infrastructure. Keep the\nprevious tag immutable and verify the replacement artifacts through the release\nworkflow. An unresolved code or artifact defect still blocks the vote.\n\n## Stop Conditions\n\nBefore creating a new tag, stop if the Git tree is dirty, the tag already\nexists, or its target would differ from the release commit. A failed workflow,\nstaging operation, or artifact check pauses the dependent step until it is\ndiagnosed and recovered under [Release retries](#release-retries); failure alone\ndoes not require a higher RC. Before sending the vote, require the selected source\ncandidate URL (ATR or manual SVN) and both closed Nexus repositories to be public,\nthe trusted-hardware report to show a complete byte-for-byte match, and tag\nworkflows to be successful unless the release manager explicitly waived monitoring.\n\n## References\n\n- [Apache Fory release guide](https:\u002F\u002Ffory.apache.org\u002Fdocs\u002Fcommunity\u002Fhow_to_release)\n- [Fory development-list archive](https:\u002F\u002Flists.apache.org\u002Flist.html?dev@fory.apache.org)\n- [Apache Pekko CI release workflow](https:\u002F\u002Fgithub.com\u002Fapache\u002Fpekko\u002Fblob\u002Fmain\u002F.github\u002Fworkflows\u002Fstage-release-candidate.yml)\n- [Sonatype Nexus 2 staging REST example](https:\u002F\u002Fsupport.sonatype.com\u002Fhc\u002Fen-us\u002Farticles\u002F213465448-Automatically-dropping-old-staging-repositories)\n","# Apache Fory Release\n\nUse `.github\u002Fworkflows\u002Fstage-release-candidate.yml` for source and JVM staging\nunless the user explicitly asks for a manual release. The workflow uses\n`ci\u002Frelease.py`; do not reproduce its source-build, JVM-publication, Nexus\nclosure, or artifact-verification logic in shell commands. Do not add unrelated\ntest runs.\n\nRelease automation, CI, and artifact-compliance fixes belong in PRs targeting\n`apache\u002Fmain`. Merge those fixes before preparing the candidate. Keep the\nversion-preparation branch local and push only the immutable RC tag; do not\npush a `releases-*` branch or target it with repair PRs unless the release\nmanager explicitly requests that separate branch workflow.\n\n## CI signing and staging prerequisites\n\nThe workflow runs only in `apache\u002Ffory` and uses these Infra-provisioned GitHub\nActions secrets:\n\n| Secret                      | Purpose                                                     |\n| --------------------------- | ----------------------------------------------------------- |\n| `FORY_GPG_SECRET_KEY`       | Import the Infra-managed CI signing key in each signing job |\n| `NEXUS_STAGE_DEPLOYER_USER` | Authenticate Java\u002FKotlin and Scala Nexus staging            |\n| `NEXUS_STAGE_DEPLOYER_PW`   | Authenticate Java\u002FKotlin and Scala Nexus staging            |\n\nSource staging uses ATR with GitHub OIDC, not SVN credentials. Do not add a\npersonal signing key, a GPG passphrase secret, or SVN credentials to this flow.\n\nSource packaging requires Syft 1.57.0. CI installs this pinned version; install\nthe same version on the trusted verification machine and put `syft` on `PATH`\n(or set `SYFT` to its executable path). The build emits a signed CycloneDX 1.6\nSBOM beside the source archive, with its own SHA-512 checksum. It inventories\nthe manifests and lock files included in the archive; it is not a complete\nresolved dependency inventory for every runtime's binaries. Dependency\nenrichment is disabled and the source commit supplies the timestamp so the\nSBOM can be compared byte-for-byte during verification.\n\nThe source archive includes `.rat-excludes` for machine-readable metadata,\nbundled license texts, and specifically attributed third-party files. Keep\nthird-party notices intact. The matching lightweight-check exclusions are in\n`.asf.yaml` under `project.policy.source_excludes_lightweight`. ASF synchronizes\nthat policy from the default branch. After merging policy changes to\n`apache\u002Fmain`, confirm the exact patterns are active in ATR before staging.\nDo not disable either license check or add broad source-directory exclusions.\n\nThe Nexus account must have staging access to the `org.apache.fory` profile.\nProvisioning the shared CI credentials alone does not grant access to this\nproject. `stage_jvm` checks profile access before building or uploading artifacts;\nif it is missing, ask Infra to grant Fory staging access to the provisioned CI\naccount. Do not replace the CI credentials with a personal account.\n\nBefore the first CI release, or after a signing-key rotation:\n\n- Obtain the CI public key and its full primary fingerprint from Infra's message\n  to the project's private mailing list. Confirm that this public key is present\n  in the published [Fory KEYS](https:\u002F\u002Fdownloads.apache.org\u002Ffory\u002FKEYS). If it is\n  absent, arrange publication of the public key before staging a candidate.\n  Keep private key material and revocation certificates out of the repository.\n- Set `gpg_fingerprint` to that independently confirmed CI key fingerprint for\n  local verification and the vote email. Do not reuse a personal signing\n  fingerprint from an earlier manual release or trust a CI log alone.\n- Merge the staging workflow to the default branch before dispatching it, and\n  create the RC from a commit that contains the workflow. Do not move an old RC\n  tag to make the workflow available.\n\nSecret provisioning and ordinary PR checks do not prove that signing, ATR\nupload, or Nexus staging works. The first authorized CI staging run must succeed,\nand its artifacts must pass the trusted-hardware verification below before voting.\n\n## Required Inputs\n\nCollect these values before starting:\n\n- `release_version`: final version without `v` or an RC suffix, such as `1.7.0`.\n- `rc`: RC suffix, such as `rc3`.\n- `previous_version`: previous release tag version, such as `1.6.1`.\n- Release discussion URL, if already known. If it is not supplied, find the\n  exact release thread in the Fory development-list archive as described below.\n\nDerive the release values:\n\n```bash\nrelease_branch=\"releases-${release_version}\"\nrc_tag=\"v${release_version}-${rc}\"\nrelease_candidate_url=\"https:\u002F\u002Freleases.apache.org\u002Fdownload\u002Fpath\u002Ffory\u002F${release_version}\"\n```\n\n### Find the release discussion\n\nIf the release discussion URL was not supplied, search the\n[Fory development-list archive](https:\u002F\u002Flists.apache.org\u002Flist.html?dev@fory.apache.org)\nfor the exact release version and a `[DISCUSS]` subject. Use the deterministic\nhelper, which accepts exactly one root discussion thread:\n\n```bash\ndiscussion_url=\"$(\n  python3 .agents\u002Fskills\u002Ffory-release\u002Fscripts\u002Ffind_discussion.py \\\n    \"$release_version\"\n)\"\n```\n\nOpen the resulting URL and verify that its subject and body discuss the exact\n`release_version`. If the automated search finds zero or multiple roots, use\nthe archive UI to search the same exact version and `[DISCUSS]`; ask the release\nmanager only if the result remains absent or ambiguous. When a URL is supplied,\nopen and verify it instead of assuming it matches this release.\n\n## Default CI Workflow\n\n### 1. Create a clean local release branch\n\nRun from the repository root. Clean means no staged, modified, or untracked files.\n\n```bash\ntest -z \"$(git status --porcelain)\"\ntest \"$(git remote get-url apache)\" = \"git@github.com:apache\u002Ffory.git\"\ngit fetch apache main --tags\ngit switch -c \"$release_branch\" apache\u002Fmain\ntest -z \"$(git status --porcelain)\"\n```\n\nFor a new release branch, stop if the branch already exists or either cleanliness check fails. To resume an existing candidate, follow [Release retries](#release-retries) instead of recreating its branch or tag. Do not remove or hide user files to make the check pass.\n\n### 2. Bump the version\n\n```bash\npython3 ci\u002Frelease.py bump_version -version \"$release_version\" -l all\ngit diff --check\ngit status --short\n```\n\nReview the version diff. Use this command directly; do not substitute another version-bump workflow.\n\n### 3. Commit the release version\n\n```bash\ngit add -u\ngit commit -m \"prepare release for ${release_version}\"\ntest -z \"$(git status --porcelain)\"\nrelease_commit=\"$(git rev-parse HEAD)\"\n```\n\nStage only the version changes produced by the release script. Keep this\nversion-preparation commit local until the RC tag is pushed in the next step.\n\n### 4. Create and push the RC tag\n\nBefore creating a new RC tag, confirm that neither the local nor remote tag already exists. Never move, delete, or overwrite a published RC tag. Retrying a workflow for its existing tag does not create a new candidate; follow [Release retries](#release-retries).\n\n```bash\ntest -z \"$(git tag --list \"$rc_tag\")\"\ntest -z \"$(git ls-remote --tags apache \"refs\u002Ftags\u002F${rc_tag}\")\"\ntest \"$(git rev-parse HEAD)\" = \"$release_commit\"\ngit tag \"$rc_tag\" && git push apache \"$rc_tag\"\ntest \"$(git rev-parse \"${rc_tag}^{commit}\")\" = \"$release_commit\"\n```\n\nThe tag starts the ecosystem package-release workflows. A later infrastructure\nfailure does not by itself change the candidate; diagnose it using\n[Release retries](#release-retries).\n\n### 5. Stage source and JVM artifacts in CI\n\nDispatch the staging workflow on the immutable RC tag:\n\n```bash\ngh workflow run stage-release-candidate.yml \\\n  --repo apache\u002Ffory \\\n  --ref \"$rc_tag\" \\\n  -f source=true \\\n  -f jvm=true\n```\n\nRecord the exact workflow run ID and URL and wait for it with\n`gh run watch --exit-status`. Do not select a run only by commit SHA because a\nmain-branch run can share the same commit. The workflow stages the signed source\narchive to Apache Trusted Release through OIDC, publishes the JVM artifacts,\nand closes the Java\u002FKotlin and Scala Nexus repositories. It does not use SVN.\n\nFrom the successful run summary, record and open both distinct Nexus staging\nrepository IDs and the ATR candidate URL. Also record the reported Java runtime\nversion and vendor for the independent rebuild:\n\n```bash\njava_kotlin_staging_id=\"orgapachefory-...\"\nscala_staging_id=\"orgapachefory-...\"\njava_runtime_version=\"...\" # Complete java.runtime.version from JVM staging\njava_vendor=\"...\" # Exact java.vendor from JVM staging\ntest -n \"$java_kotlin_staging_id\"\ntest -n \"$scala_staging_id\"\ntest \"$java_kotlin_staging_id\" != \"$scala_staging_id\"\n```\n\nKeep both repositories closed during the vote. Do not promote them until the\nvote passes.\n\n### 6. Check the tag-triggered workflows\n\nInspect every workflow triggered by the tag. Filter by the tag rather than only\nby commit SHA so main-branch runs at the same commit are not mixed into the\nresult. By default, wait for every run and require successful conclusions:\n\n```bash\npython3 .agents\u002Fskills\u002Ffory-release\u002Fscripts\u002Fcheck_tag_workflows.py \\\n  --repo apache\u002Ffory \\\n  --tag \"$rc_tag\" \\\n  --commit \"$release_commit\" \\\n  --watch\n```\n\nThe helper re-queries by tag after waiting to catch later-created runs. A failed\nrun requires diagnosis, not an automatic RC increment. For a transient failure,\nrerun only the failed jobs with `gh run rerun \u003Crun-id> --repo apache\u002Ffory --failed`,\nthen run the helper again for the same tag and commit.\n\nIf the release manager explicitly waives workflow monitoring for a particular RC, run\nthe same command with `--allow-incomplete` instead of `--watch`, and record the\nsnapshot IDs, states, and reason. Do not cancel the remote workflows or report\nincomplete runs as successful.\n\n### 7. Verify all CI artifacts on trusted hardware\n\nDo not run this comparison in GitHub Actions. Use the independently confirmed\nInfra-managed CI key fingerprint from the prerequisites. Install the same JDK\ndistribution and complete runtime version recorded by JVM staging, including the\nbuild suffix, and set `JAVA_HOME` and `PATH` to it. Then run the repository\nverifier on a machine controlled by the release manager:\n\n```bash\n: \"${gpg_fingerprint:?missing CI signing-key fingerprint}\"\npython3 ci\u002Frelease.py verify_ci_artifacts \\\n  -v \"$release_version\" \\\n  --rc-tag \"$rc_tag\" \\\n  --java-kotlin-id \"$java_kotlin_staging_id\" \\\n  --scala-id \"$scala_staging_id\" \\\n  --gpg-fingerprint \"$gpg_fingerprint\" \\\n  --java-runtime-version \"$java_runtime_version\" \\\n  --java-vendor \"$java_vendor\" \\\n  --source-url \"$release_candidate_url\"\n```\n\nThe command checks out the exact RC commit in a temporary clone, rebuilds the\nsource archive, source SBOM, and complete JVM publication without signing or upload\ncredentials, verifies the staged signatures with the public key, and compares\nevery source, JAR, POM, source JAR, documentation JAR, and distribution file\nbyte-for-byte. Each JVM ecosystem is built once and may reuse the machine's\nnormal dependency caches; only source and build outputs are clean. It writes a\nMarkdown report under `dist\u002F`. Any mismatch or missing artifact blocks the vote.\nBefore downloading or rebuilding, the verifier requires an OpenJDK 25 runtime\nwhose `java.runtime.version` and `java.vendor` exactly match the supplied staging\nvalues. Matching only the Java major version is insufficient. The verifier also\nrequires the expected public key in `KEYS`;\nlocal personal keyrings are not used to satisfy this check.\nFailed verification retains the local rebuild and downloaded artifacts beside\nthe report for diagnosis; successful verification removes these temporary files.\nAfter a download failure, retry with `--rebuild-dir \u003Cretained-directory>` to\nreuse the completed unsigned build on the same machine without recompiling.\nThe completed rebuild must have a matching JDK record; a missing or different\nrecord requires a fresh build. The checkout must still match the RC commit and\nremain unchanged. Downloads,\nsignature checks, and every byte comparison run again; retained files are not\ndeleted in this mode.\nSource packaging uses a direct `git archive` of the RC tag without rewriting\n`LICENSE`, creating commits, or moving refs. Benchmark-specific attribution stays\nin `benchmarks\u002FLICENSE` and `benchmarks\u002FNOTICE` with the excluded benchmark sources.\n\n### 8. Draft the vote email\n\nLoad only the release-manager identity from `.local\u002Ffory-release.env` when\ndrafting the email. Never commit this ignored file or store release secrets in\nit.\n\n```bash\nrelease_config=\"$(git rev-parse --show-toplevel)\u002F.local\u002Ffory-release.env\"\ntest -f \"$release_config\"\n. \"$release_config\"\nrelease_manager_name=\"${FORY_RELEASE_MANAGER_NAME:?missing release manager name}\"\n```\n\nRead [the vote email template](assets\u002Fvote-email.txt) and produce a complete,\ncopyable email. Fill every placeholder from verified output, attach the\ntrusted-hardware report or link an existing public copy, and state that the vote\nremains open for at least 72 hours without specifying a closing date or time.\nDo not send the email unless requested.\n\n## Explicit Manual Workflow\n\nOnly when the user explicitly requests manual publishing, read and follow\n[the manual release workflow](references\u002Fmanual-release.md). Do not fall back\nto it automatically after a CI failure.\n\n## Verification-Only Requests\n\nFor an existing candidate, do not create another tag or staging repository.\nConfirm the exact tag, commit, source URL (ATR or manual SVN), both Nexus\nrepository IDs, and signing-key fingerprint from the vote. Check the tag workflows\nand run step 7 against those artifacts. Rebuild the unmodified RC checkout, not\nthe verifier's branch; never copy newer POMs or sources into the RC to force a\nmatch. Report any mismatch against the original candidate.\n\n## GitHub Release Title and Notes\n\nWhen authorized to create the final GitHub Release after the vote passes:\n\n- Set the title to the version tag alone, such as `v1.7.6`, not\n  `Apache Fory 1.7.6`. Use `--title \"v${release_version}\"` when creating it with\n  `gh release create`.\n- Put important features in a `## Highlights` section before the full change\n  list. Give each important feature its own named `###` subsection rather than\n  leaving it only as an entry in the change list. Explain what users can do with\n  it and include a concise example or documentation link where useful.\n- Describe only features included in that release; preserve the complete\n  change list after the highlights.\n\n## Release retries\n\nAn RC identifies the release content under review, not a CI attempt. Inspect the\nfailed step and its logs before deciding how to recover. Network timeouts,\ndependency-download failures, runner failures, and interrupted status checks do\nnot by themselves invalidate an unchanged candidate.\n\nWithout a substantive release change, keep the same release commit and RC tag\nand resume only the failed or incomplete steps. Preserve verified Maven staging\nrepositories and source artifacts; do not rebuild or republish successful\nartifacts merely because an unrelated CI job failed. Before retrying a push,\nupload, Nexus action, or SVN commit, inspect remote state because an interrupted\nrequest may already have succeeded. Use the Nexus reference's `--verify-only`\npath for repositories that are already closed.\n\nCreate a higher RC only when a substantive fix changes the release content,\nsuch as source, dependencies, build inputs, or packaging. Commit the actual fix\nbefore tagging the replacement; do not create an empty commit or a second RC\nat the same unchanged release commit just to retry infrastructure. Keep the\nprevious tag immutable and verify the replacement artifacts through the release\nworkflow. An unresolved code or artifact defect still blocks the vote.\n\n## Stop Conditions\n\nBefore creating a new tag, stop if the Git tree is dirty, the tag already\nexists, or its target would differ from the release commit. A failed workflow,\nstaging operation, or artifact check pauses the dependent step until it is\ndiagnosed and recovered under [Release retries](#release-retries); failure alone\ndoes not require a higher RC. Before sending the vote, require the selected source\ncandidate URL (ATR or manual SVN) and both closed Nexus repositories to be public,\nthe trusted-hardware report to show a complete byte-for-byte match, and tag\nworkflows to be successful unless the release manager explicitly waived monitoring.\n\n## References\n\n- [Apache Fory release guide](https:\u002F\u002Ffory.apache.org\u002Fdocs\u002Fcommunity\u002Fhow_to_release)\n- [Fory development-list archive](https:\u002F\u002Flists.apache.org\u002Flist.html?dev@fory.apache.org)\n- [Apache Pekko CI release workflow](https:\u002F\u002Fgithub.com\u002Fapache\u002Fpekko\u002Fblob\u002Fmain\u002F.github\u002Fworkflows\u002Fstage-release-candidate.yml)\n- [Sonatype Nexus 2 staging REST example](https:\u002F\u002Fsupport.sonatype.com\u002Fhc\u002Fen-us\u002Farticles\u002F213465448-Automatically-dropping-old-staging-repositories)\n",{"name":5,"description":7},"main","0e9c34aeaacfcea22c09a654cc3b2c8f582492b6",".agents\u002Fskills\u002Ffory-release",471,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory","https:\u002F\u002Ffory.apache.org","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-14 09:50:03",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add apache\u002Ffory --skill fory-release",{"tool":58,"command":59},"bunx","bunx skills add apache\u002Ffory --skill fory-release",{"tool":61,"command":62},"pnpm","pnpm dlx skills add apache\u002Ffory --skill fory-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-release\u002FSKILL.md",true,[66,72,78,82,88],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Fvote-email.txt","ASSET","资产文件",1838,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-release\u002Fassets\u002Fvote-email.txt",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fmanual-release.md","REFERENCE","参考文档",5123,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-release\u002Freferences\u002Fmanual-release.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fnexus-staging.md",2860,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-release\u002Freferences\u002Fnexus-staging.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fcheck_tag_workflows.py","SCRIPT","脚本",5481,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-release\u002Fscripts\u002Fcheck_tag_workflows.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Ffind_discussion.py",3853,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-release\u002Fscripts\u002Ffind_discussion.py",[93,122],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":38},"01M6ACYT2JX3ZBRH1KP0X4H1BC","fory-version-bump","Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C#, Dart, JavaScript, Swift, integration tests, examples, and source docs. Use when preparing a release version, moving main to the next development version, switching install docs to a released version, or auditing Fory version consistency after release scripts run.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-version-bump\u002FSKILL.md",[],[100,101,21,102,103,9,104,19,105,106,107,108,109,110,111,112,20,113,43,114,115,116,117,26,30,118,119,120,121],"bump","fory version bump","version","version bump","javascript","java","run","development","scala","integration tests","examples","go","integration","install","next","across","switching","scripts","rust","swift","docs","python",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":38},"01M6ACYJM1XYHYXN4MKB975WX9","fory-performance-optimization","Run profile-driven bottleneck optimization across Apache Fory implementations (Java, C++, Python\u002FCython, Go, Rust, Swift, C#, JavaScript\u002FTypeScript, Dart, Kotlin, Scala). Use when improving serialize\u002Fdeserialize throughput or latency, recovering regressions against a reference commit, diagnosing flamegraphs, fixing perf-related CI failures, or porting proven optimizations across languages without protocol or API regressions.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ffory\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffory-performance-optimization\u002FSKILL.md",[],[129,130,21,131,132,105,133,111,121,118,104,134,108,135,106,136,9,137,138,139,115,140,141,30,119],"performance optimization","Optimization","fory performance optimization","performance","typescript","commit","perf","protocol","ci","api","bottleneck","throughput","porting"]