[Jane Chu (janechu)]

Pull Request

📖 Description

Prepares @microsoft/fast-build 0.14.0, including authored binding spans and structured errors with source locations.

Generated with npm run bump: synchronizes microsoft-fast-build and microsoft-fast-convert to 0.14.0, updates workspace dependency ranges and lockfiles, generates changelogs, and consumes all four pending change files. @microsoft/fast-element remains 3.1.2; its documentation-only change is recorded without a version bump.

🎫 Issues

Releases the changes for #7763 and #7750, implemented in #7768 and #7769.

👩‍💻 Reviewer Notes

This is a metadata-only bump PR on the documented publish_<timestamp> branch. It creates no release/tag and publishes no packages. The release preview identifies only @microsoft/fast-build@0.14.0, bundled with both synchronized Rust crates.

Existing change files are consumed rather than adding another change file. npm run checkchange passes through the documented publish-branch/admin policy. Generated consumer dependency updates do not add other package version bumps.

Refreshing all local tags encountered pre-existing historical local/remote tag conflicts; no tags were overwritten. The relevant remote release tags were checked separately, and the new 0.14.0 tag does not exist.

📑 Test Plan

Command	Result
npm run bump	Passed: generated versions, changelogs, dependency updates, and paired Rust synchronization
node build/scripts/create-github-releases.mjs --check-only	Passed: only fast-build 0.14.0 and both bundled Rust crates need a release
cargo metadata --manifest-path crates/microsoft-fast-build/Cargo.toml --no-deps --locked --format-version 1	Passed: locked package version is 0.14.0
cargo metadata --manifest-path crates/microsoft-fast-convert/Cargo.toml --no-deps --locked --format-version 1	Passed: locked package version is 0.14.0
npm run build	Passed: all 9 workspace tasks
npm run test	Passed: 6 tasks succeeded; 8 skipped by Lage
npm pack --dry-run --json -w @microsoft/fast-build	Passed: version 0.14.0 includes both rebuilt WASM modules; no tarball published
npm run biome:check -- -- --no-errors-on-unmatched	Passed: no eligible source files in this generated-only diff
npm run format:check	Passed: no eligible files selected
npm run checkchange	Passed: publish-branch/admin policy verified

No new tests are needed for generated version/changelog metadata.

✅ Checklist

General

• I have included a change request file using $ npm run change
• I have added tests for my changes.
• I have tested my changes.
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation and followed the standards for this project.

Agents

• I have linked to an existing issue in this project that this change addresses
• I have read the skills
• I have read the DESIGN.md file(s) in packages relevant to my changes
• I have updated the DESIGN.md file(s) in packages relevant to my changes

⏭ Next Steps

After human review and merge, the existing GitHub release/Azure CD flow can create and publish the release artifacts.