Skip to content

Weekly publish of pre-release - #108

Merged
carole-lavillonniere merged 6 commits into
localstackfrom
cosy-807-auto-release-the-lambda-rie-lambda-runtime-init-so-its-go
Aug 13, 2026
Merged

Weekly publish of pre-release#108
carole-lavillonniere merged 6 commits into
localstackfrom
cosy-807-auto-release-the-lambda-rie-lambda-runtime-init-so-its-go

Conversation

@carole-lavillonniere

@carole-lavillonniere carole-lavillonniere commented Jun 30, 2026

Copy link
Copy Markdown

Towards COSY-807.

  • Auto-publish a prerelease of RIE every Friday mornings at 6am UTC, if there are new commits.
  • A new tag with bumped patch is pushed (latest version is fetched from Github releases).
  • The goal is to have vulnerabilities auto-resolve weekly without human intervention.
  • Release can still be done manually if needed
  • If the release job fails, we notify slack channel #core-systems-notifications

Related:

Cut a new patch release once a week when there are new commits on
localstack, so Go-dep/stdlib CVE fixes self-publish without a manual tag.

- weekly-release.yml: Friday cron + workflow_dispatch; discovers the latest
  published release, patch-bumps, skips if no new commits, then calls build.yml.
- build.yml: add workflow_call with an optional version input so the same
  test -> build -> release path publishes the computed version (no PAT needed).
@carole-lavillonniere carole-lavillonniere changed the title Add weekly auto-release workflow for the LocalStack RIE Weekly auto-release Jun 30, 2026
@carole-lavillonniere
carole-lavillonniere marked this pull request as ready for review June 30, 2026 14:26

@dfangl dfangl left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I am not super happy with the workflow call, but sadly pushes from the github action do not trigger more actions, so this is all we can do I think :P

However, we never really create a tag, right? I think the release action will not create one, and instead this fails. Could you double check or push a tag in the weekly-release workflow?

@carole-lavillonniere

Copy link
Copy Markdown
Author

I am not super happy with the workflow call, but sadly pushes from the github action do not trigger more actions, so this is all we can do I think :P

However, we never really create a tag, right? I think the release action will not create one, and instead this fails. Could you double check or push a tag in the weekly-release workflow?

Added a step to push the tag: 2e08a7d
Since we cannot run this workflow without merging it first, tested by forking the repo and running the workflow here: https://github.com/carole-lavillonniere/lambda-runtime-init/actions/runs/31389766763

@carole-lavillonniere
carole-lavillonniere marked this pull request as draft August 12, 2026 10:06
@carole-lavillonniere carole-lavillonniere changed the title Weekly auto-release Weekly publish of pre-release Aug 12, 2026
@carole-lavillonniere
carole-lavillonniere marked this pull request as ready for review August 13, 2026 12:00

@dfangl dfangl left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM now!

@carole-lavillonniere
carole-lavillonniere merged commit 3cf0464 into localstack Aug 13, 2026
3 checks passed
@carole-lavillonniere
carole-lavillonniere deleted the cosy-807-auto-release-the-lambda-rie-lambda-runtime-init-so-its-go branch August 13, 2026 12:49
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