Configure bumpver for Concourse release pipeline - #3220
Merged
Conversation
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Pull request overview
Adds bumpver configuration so the Concourse release pipeline can automatically bump the app’s release version using a date-based scheme.
Changes:
- Add
[tool.bumpver]configuration topyproject.toml, including file patterns for version replacement. - Update
main/settings.pyVERSIONconstant to the newYYYY.MM.DD.Nformat.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
pyproject.toml |
Adds bumpver config and a file pattern intended to update the Django VERSION string during releases. |
main/settings.py |
Updates the VERSION constant to the initial date-based release version used by the pipeline. |
blarghmatey
force-pushed
the
configure-bumpver
branch
2 times, most recently
from
April 27, 2026 18:42
8e8a5d4 to
f9f0bc9
Compare
OpenAPI ChangesNo changes detected Unexpected changes? Ensure your branch is up-to-date with |
blarghmatey
force-pushed
the
configure-bumpver
branch
from
April 29, 2026 13:22
86e0749 to
0912488
Compare
blarghmatey
force-pushed
the
configure-bumpver
branch
from
June 4, 2026 19:37
a164ef7 to
9126e28
Compare
feoh
approved these changes
Jun 10, 2026
ChristopherChudzicki
added a commit
that referenced
this pull request
Jul 10, 2026
* Sync pyproject.toml version with settings.py VERSION (0.73.4) pyproject.toml's [project].version was reset to 0.70.10 in #3220 while settings.py VERSION is 0.73.4, breaking test_bump_my_version_format on main (and every branch cut from it). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Sync uv.lock mit-learn version to 0.73.4 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What are the relevant tickets?
N/A
Description (What does it do?)
Adds
[tool.bumpver]configuration topyproject.tomlso the Concourserelease pipeline can update the application version automatically on each
release.
The new version format is
YYYY.MM.DD.N(e.g.,2026.04.16.1), whichreplaces the previous semver-style version strings. This is required by the
Concourse
releaseresource workflow being rolled out inmitodl/ol-infrastructure#4506.
The
VERSIONconstant in Django settings is updated to the initial releaseformat version as part of this change.
How can this be tested?
bumpverinstalled (pip install bumpver), runbumpver update --dryfrom the repo root and confirm it shows the expected diff with no errors.VERSIONin Django settings matchescurrent_versioninpyproject.toml.Additional Context
Part of the Concourse release pipeline modernization — migrating from the Doof
Slack bot to a Concourse-native release workflow using GitHub Issues as
production gates.