Skip to content

fix: correct target_api_version to 0.1.0 in release-plan.yaml - #23

Merged
ALIIQBAL786 merged 3 commits into
camaraproject:mainfrom
ALIIQBAL786:fix/release-plan-version
Oct 15, 2026
Merged

ALIIQBAL786 merged 3 commits into
camaraproject:mainfrom
ALIIQBAL786:fix/release-plan-version

Conversation

@ALIIQBAL786

Copy link
Copy Markdown
Contributor

The automation appends the pre-release suffix itself based on target_release_type. Setting 0.1.0-alpha.1 resulted in a double suffix (0.1.0-alpha.1-alpha.1). Correct value is 0.1.0.

The automation appends the pre-release suffix itself based on
target_release_type. Setting 0.1.0-alpha.1 resulted in a double
suffix (0.1.0-alpha.1-alpha.1). Correct value is 0.1.0.
@ALIIQBAL786

Copy link
Copy Markdown
Contributor Author

Hi @usmanTheCoder, quick one — could you approve this? It's a one-line fix to the release-plan.yaml version so the automation generates the correct 0.1.0-alpha.1 instead of 0.1.0-alpha.1-alpha.1.

Comment thread release-plan.yaml Outdated
Comment on lines 28 to 29

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not directly related to this PR, but you should use Commonalities r4.4 and ICM r4.2, which are the current ones. r3.4 was the base of Fall25 meta-release.

Update to current dependency versions per hdamker feedback:
- commonalities_release: r3.4 -> r4.4
- identity_consent_management_release: r3.3 -> r4.2

r3.x versions were from Fall25 meta-release, not current.
@ALIIQBAL786

Copy link
Copy Markdown
Contributor Author

Thanks @hdamker, updated the dependency versions to Commonalities r4.4 and ICM r4.2. @usmanTheCoder could you approve when you get a chance?

… r4.4

Commonalities r3.4 = 0.6.1, r4.4 = 0.9.0. Aligning the spec with
the updated dependency declared in release-plan.yaml.
@ALIIQBAL786
ALIIQBAL786 merged commit 4e9727d into camaraproject:main Oct 15, 2026
1 of 2 checks 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.

3 participants