Skip to content

vault: migrate stable/1.8 to charmcraft 3.x#93

Merged
MylesJP merged 1 commit into
openstack-charmers:mainfrom
freyes:vault-1.8-charmcraft-3.x
Jun 8, 2026
Merged

vault: migrate stable/1.8 to charmcraft 3.x#93
MylesJP merged 1 commit into
openstack-charmers:mainfrom
freyes:vault-1.8-charmcraft-3.x

Conversation

@freyes

@freyes freyes commented Jun 5, 2026

Copy link
Copy Markdown
Member

The stable release of vault 1.8 is getting noble support, to achieve this it was needed to migrate it charmcraft-3.x, this updates the Launchpad recipe.

References: https://review.opendev.org/c/openstack/charm-vault/+/990213/

The stable release of vault 1.8 is getting noble support, to achieve
this it was needed to migrate it charmcraft-3.x, this updates the
Launchpad recipe.

References: https://review.opendev.org/c/openstack/charm-vault/+/990213/
Signed-off-by: Felipe Reyes <felipe.reyes@canonical.com>
@freyes freyes requested a review from MylesJP June 5, 2026 21:44

@MylesJP MylesJP left a comment

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.

LGTM

@MylesJP MylesJP merged commit 53f3ca2 into openstack-charmers:main Jun 8, 2026
5 checks passed
openstack-mirroring pushed a commit to openstack/charm-vault that referenced this pull request Jun 8, 2026
Summary:
- Use charm 3.x/stable
- Use charmcraft 3.x/stable
- Build binary python packages
- Use branches when available in the build.lock
- Use setuptools-68.2.2 (compatible with py312)
- Use pbr-7.0.3 (compatible with py312)
- Add py312 tox target
- Add ubuntu@24.04 base to build/run on.
- Use charms.reactive 1.5.3 (compatible with py312)
- Switch to stable/caracal git branches
- Gate on charmbuild zuul job
- Drop unused scripts
- Refresh src/build.lock to make it compatible with py312

References: openstack-charmers/charmed-openstack-info#93
Signed-off-by: Felipe Reyes <felipe.reyes@canonical.com>
Change-Id: Ia50d2460260f58c2f32489e61b4b0cc1a6ef72da
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.

2 participants