Skip to content

Sync release 0.2.7 to develop - #37

Open
inditextechbot[bot] wants to merge 4 commits into
developfrom
automated/sync-release-0.2.7-to-develop
Open

Sync release 0.2.7 to develop#37
inditextechbot[bot] wants to merge 4 commits into
developfrom
automated/sync-release-0.2.7-to-develop

Conversation

@inditextechbot

Copy link
Copy Markdown

Automated pull request syncing the release cut on main back into develop.

ivanasabi and others added 4 commits September 4, 2026 21:58
* fix: reconcile canary version with Maven Central

0.2.6 was published to Maven Central during the D12/D17 delegated-release
proof (dev.inditex:mavencentral-ci-testing-core, -core, -aggregate and the
parent, all at 0.2.6). Maven Central is immutable, so that coordinate can
never be reused, but this repository still declared 0.2.6-SNAPSHOT and
carried no 0.2.6 tag: the next release would have computed 0.2.6 and failed
against Central after already moving the baseline branch.

Move the reactor to 0.2.7-SNAPSHOT so the next release cuts a coordinate that
is actually free. This is the next-development-iteration bump that the proof
run performed on its own throwaway branch and therefore never reached main.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: record the version reconcile in the changelog

The release-preview gate requires every release-bearing pull request to say
what it releases. This one moves the reactor off a coordinate Maven Central
has already made immutable, which is exactly the kind of change the log
exists to record.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

1 participant