Weekly publish of pre-release - #108
Merged
carole-lavillonniere merged 6 commits intoAug 13, 2026
Merged
Conversation
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
changed the title
1 task
carole-lavillonniere
marked this pull request as ready for review
June 30, 2026 14:26
carole-lavillonniere
requested review from
dfangl,
dominikschubert and
joe4dev
as code owners
June 30, 2026 14:26
dfangl
requested changes
Jul 2, 2026
dfangl
left a comment
dfangl
left a comment
Member
There was a problem hiding this comment.
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?
Author
Added a step to push the tag: 2e08a7d |
carole-lavillonniere
marked this pull request as draft
August 12, 2026 10:06
carole-lavillonniere
changed the title
carole-lavillonniere
marked this pull request as ready for review
August 13, 2026 12:00
carole-lavillonniere
deleted the
cosy-807-auto-release-the-lambda-rie-lambda-runtime-init-so-its-go
branch
August 13, 2026 12:49
dfangl
pushed a commit
that referenced
this pull request
Sep 1, 2026
…131) * ci: make a missing Slack webhook a clear failure, not a cryptic one The weekly release failed on Aug 28 and the alert never reached Slack. The notify job failed with: Missing input! Either a method or webhook is required to take action. COSY_WEBHOOK_URL resolves to an empty string, so GitHub omits the `webhook` input entirely and the action rejects the call. The secret exists but was created 2026-08-12 and never updated -- one day before the weekly release workflow landed in #108 -- and the notify path was not exercised until the Aug 28 failure, so this alert has never worked. Check the webhook in a preflight step that names the missing secret, and set errors: true so Slack-side delivery failures fail the step instead of reporting green. Neither change can populate the secret; that still needs setting in repo settings. They make the next failure say so in one line. * ci: send the Slack payload as JSON with a literal-newline message slack-github-action v4 ships js-yaml v5, which enforces stricter multiline indentation. MESSAGE was a double-quoted YAML scalar, so its \n\n became real newlines that were interpolated into the YAML payload at column 0 and broke the document: Invalid input! Failed to parse contents of the provided payload SyntaxError: Expected property name or '}' in JSON at position 1 Single-quote MESSAGE so \n stays a two-character escape, and send the payload as JSON, where an interpolated message cannot break the structure and \n is exactly the newline Slack mrkdwn renders. Verified end to end on a throwaway branch: the notify job was forced to run under dryRun and delivered to Slack with errors: true, so a rejected delivery would have failed the step. * ci: drop explanatory comments from the notify job
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.
Towards COSY-807.
Related: