chore(deps): bump OMT-Global/bootstrap/.github/workflows/release-preflight-reusable.yml from 848846fc40b02c512e2b86d23bb1b295f7908f8a to 3b8584b78f253b72cfee0a798f9314028549302c

[dependabot]

Bumps OMT-Global/bootstrap/.github/workflows/release-preflight-reusable.yml from 848846f to 3b8584b.

Changelog

Sourced from OMT-Global/bootstrap/.github/workflows/release-preflight-reusable.yml's changelog.

Governed Release Train

This repository uses release maturity level governed.

Manual Flow

1. Open a release train issue with .github/ISSUE_TEMPLATE/release_train.yml.
2. Create or update the release/{major}.{minor} release branch.
3. Run Release Preflight with the candidate version, channel, target ref, and release issue.
4. Copy the successful preflight run ID into the release issue.
5. Run Full Release Validation against the same target ref.
6. Copy the successful validation run ID into the release issue.
7. Create the exact release tag only after validation evidence exists.
8. Run Release Publish with the tag, preflight run ID, validation run ID, channel, and release issue.
9. Run or review Release Postpublish, then close or supersede the release issue.

Publish must consume the artifact bundle proven by preflight. If the preflight artifact cannot be downloaded or its recorded target SHA differs from the tag SHA, publish must fail instead of rebuilding.

Customization

Repo-specific behavior belongs in these hook scripts:

• scripts/release/prep.sh
• scripts/release/preflight.sh
• scripts/release/validate.sh
• scripts/release/build.sh
• scripts/release/publish.sh
• scripts/release/postpublish.sh

The generated defaults do not require secrets and do not publish external packages.

Commits

• 3b8584b chore(deps): bump OMT-Global/bootstrap/.github/workflows/release-postpublish-...
• 124abd5 chore(deps-dev): bump tsx in the npm-minor-patch group (#128)
• ce817cb chore(deps): bump OMT-Global/bootstrap/.github/workflows/release-publish-reus...
• e99709d chore(deps): bump OMT-Global/bootstrap/.github/workflows/release-preflight-re...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)