Repository navigation
chore(release): bump product_version to 1.2.0 on main - #518
Merged
Merged
Conversation
After GA 1.1.0, main snapshot builds should publish 1.2.0-SNAPSHOT. Add 1.1 to backport targets for the maintenance line.
erikcurrin-elastic
approved these changes
Oct 6, 2026
5 of 12 tasks
Jan-Kazlouski-elastic
added a commit
that referenced
this pull request
Oct 6, 2026
Backport of #518 for the **`1.1`** maintenance branch. On **`main`**, #518 set `product_version` to **1.2.0** (next minor / `1.2.0-SNAPSHOT`). On **`1.1`**, the next release after shipped GA **1.1.0** is patch **1.1.1**, so this PR sets `product_version` to **1.1.1** — not `1.2.0`. Also adds **`1.1`** to `.backportrc.json` `targetBranchChoices` (same backport-target change as #518). ### Checklists #### Pre-Review Checklist - [x] This PR does NOT contain credentials of any kind, such as API keys or username/passwords (double check `crawler.yml.example` and `elasticsearch.yml.example`) - [x] This PR has a meaningful title - [ ] This PR links to all relevant GitHub issues that it fixes or partially addresses - [x] this PR has a thorough description - [ ] Covered the changes with automated tests - [x] Tested the changes locally - [x] Added a label for each target release version (example: `v0.1.0`) - [ ] Considered corresponding documentation changes - [ ] Contributed any configuration settings changes to the configuration reference - [ ] Ran `make notice` if any dependencies have been added #### Changes Requiring Extra Attention - [ ] Security-related changes (encryption, TLS, SSRF, etc) - [ ] New external service dependencies added. ### Related Pull Requests * #518 ### Release Note No user-facing runtime change. Release engineering only: the **`1.1`** branch is prepared for the next patch GA (**1.1.1**) after **1.1.0**. Co-authored-by: Jan-Kazlouski-elastic <jan.kazlouski@elastic.co>
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
2 participants
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.
Open Crawler 1.1.0 is already published as a GA container image. The
product_versionfile onmainstill read 1.1.0, so Buildkite snapshot builds onmaincontinued to tag1.1.0-SNAPSHOT— a pre-release label for a version that has already shipped.This PR sets
product_versionto 1.2.0 so ongoingmainsnapshot builds target1.2.0-SNAPSHOT(the next minor line). It also adds branch1.1to.backportrc.jsonso patch backports can target the 1.1.x maintenance line (follow-up: bumpproduct_versionon1.1to 1.1.1 via backport).Checklists
Pre-Review Checklist
crawler.yml.exampleandelasticsearch.yml.example)v0.1.0)make noticeif any dependencies have been addedChanges Requiring Extra Attention
Related Pull Requests
Release Note
No user-facing runtime change. Release engineering only:
mainCI snapshots will use the 1.2.0-SNAPSHOT tag after merge.