snyk-workshops/Confluence release summary
Summarise a project with Gemini and update an existing Confluence page. Runs on major and minor releases only; patch releases are a no-op.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| gemini-api-key | Google AI Studio API key. | yes | — |
| gemini-model | Gemini model id. Kept configurable because these churn fast: 2.0-flash was shut down in March 2026 and 2.5-flash is already deprecated. Bump this rather than editing the script. | no | gemini-3.6-flash |
| confluence-base-url | e.g. https://yourorg.atlassian.net/wiki | yes | — |
| confluence-email | Atlassian account the API token belongs to. | yes | — |
| confluence-api-token | Atlassian API token (id.atlassian.com → API tokens). | yes | — |
| confluence-page-id | Numeric id of the EXISTING page to update. The action never creates a page, so a wrong id fails loudly instead of scattering stray pages in a space. | yes | — |
| version | Version being released. Defaults to the triggering tag. | no | "" |
| release-notes | Release notes to feed the model alongside the docs. | no | "" |
| extra-docs | Extra files to summarise in addition to README.md, comma or newline separated. Missing files are skipped with a note. | no | "" |
| dry-run | Generate and print the page, publish nothing. | no | false |
| force | Publish even when this isn't a major/minor bump. The version gate exists to stop automated churn, not to overrule someone who explicitly asked — set this for manual runs. | no | false |
Outputs
| name | description |
|---|---|
| published | "true" when a page was written; "false" for a patch release or a dry run. |