Repository navigation
fix(hidi): separate v2 versions and route releases by component tag - #898
Merged
Gavin Barron (gavinbarron) merged 4 commits intoOct 9, 2026
Merged
Gavin Barron (gavinbarron) merged 4 commits into
Gavin Barron (gavinbarron) merged 4 commits into
Conversation
Use the existing pinned release-please engine with exact component path exclusions and an isolated, tag-free Hidi version PR lifecycle. Preserve OData releases, baseline versions, and protected publishing gates; verify real generated plans, repeated cycles, and measured runner coverage. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2dc4344a-fac5-4e6e-89f8-eb2c9467edd4
Count open version PRs independently of seeded merged checkpoints so the full release-please suite continues to pass after the manifest advances. Verified all 80 cases against both the current and a generated future Hidi baseline. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2dc4344a-fac5-4e6e-89f8-eb2c9467edd4
Follow the user-provided release-please configuration pattern with one shared config and manifest, independent component versions, and the existing stock action. Remove custom runner, npm tooling, test/coverage machinery, labels and duplicate Hidi scaffolding. Use the supported separate-pull-requests option to preserve componentless OData releases; keep package baselines and protected production publishers unchanged. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2dc4344a-fac5-4e6e-89f8-eb2c9467edd4
Release only OData for v2 tags and Hidi for hidi-v2 tags. Validate exact project/tag versions before artifact staging, select exact component packages and GitHub assets, and stop publishing after guard failures. Use supported DotNetCoreCLI pack inputs so the OData job does not default to packing Hidi and GUI projects or rebuilding signed binaries. Preserve existing protected environments, signing connections, Hidi publishing-off flag, private-feed behavior and migration floors. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2dc4344a-fac5-4e6e-89f8-eb2c9467edd4
|
Peter Ombwa (peombwa)
approved these changes
Oct 9, 2026
Gavin Barron (gavinbarron)
deleted the
gavinbarron-hidi-v2-automated-versioning
branch
October 9, 2026 22:27
12 of 19 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
Implements the user's standard multi-component versioning pattern from
a65052d57fa5e623c765024fb05a0384691a9168and the follow-up request: “The ADO pipeline that handles releases should be updated so that it only releases the component belonging to the triggering tag.”.) and Hidi (src/Microsoft.OpenApi.Hidi). Preserve the existing bootstrap, action/token pins, independent baselines OData 2.2.1 / Hidi 2.12.2, project XML updaters, changelogs and tag conventions.separate-pull-requests: trueoption to preserve OData's existing componentless tag lifecycle; the stock engine otherwise fails to produce an OData candidate for a componentless root-only combined PR..azure-pipelines/ci-build.yml) only to v2. tags* and the dedicated Hidi pipeline (.azure-pipelines/hidi-release.yml) only to hidi-v2. tags*. Validate exact project/tag versions before staging artifacts; reject malformed, wrong-component, other-major, or mismatched manually selected tags.DotNetCoreCLI@2pack inputs: the oldprojects/argumentsinputs are ignored forcommand: pack, defaulting to all projects. Use supportedpackagesToPack, configuration/output, no-build, symbols/source and format inputs so only OData is packaged and signed binaries are not rebuilt.Validation
All tooling and fixtures are session-only; no new test framework or workflow is committed.
Safety
Hidi publishing remains false. Protected environments, signing Yuriy Semchyshyn (@5), ESRP akari (@14), service connections, resource permissions, private-feed/BuildKit-secret handling, public-only Docker context and migration floors are unchanged. Ordinary branch/PR validation is retained; release stages remain tag-only. No actual tags/releases or publishing runs were created or queued, and no permissions were granted.
Both project baselines remain unchanged. SonarCloud/CI-CD are unchanged; no custom versioning runtime remains. Canonical imported ancestry is preserved through normal additional commits, not history rewriting. No auto-merge is configured; parent coordinates v2-first landing and the separate main counterpart.