Dependabot and releases
Every SDK repository Octri generates on GitHub keeps itself up to date. Dependabot proposes dependency updates each week, and each version tag becomes a GitHub Release with its changelog as the notes.
It's on for every SDK, with nothing to set up. The two files arrive with the SDK's source when Octri publishes it to GitHub.
Dependency updates
The repository gets .github/dependabot.yml, which asks Dependabot for two weekly updates:
- the SDK's own dependencies, through its language's package manager
- the actions its workflows use
Each arrives as one grouped pull request rather than one per package, so the SDK's quality workflow checks the whole update together before you merge it.
| Language | Dependabot ecosystem |
|---|---|
| TypeScript | npm |
| Python | pip |
| Go | gomod |
| Java | maven |
| Kotlin | gradle |
| PHP | composer |
| Rust | cargo |
| Ruby | bundler |
| Dart | pub |
| Swift | swift |
Releases
The repository also gets .github/workflows/release.yml. When a tag starting with v is pushed, such as v1.2.0, it publishes a GitHub Release named after the tag:
- The notes are that version's section of
CHANGELOG.md, the text under## 1.2.0or## [1.2.0]. - If the changelog has no section for the version, GitHub's generated notes are used instead.
- A release that already exists for the tag is left alone.
Octri's own git-tag publishing pushes tags through the Octri GitHub App, which starts the workflow, and so does a maintainer pushing a tag by hand. See versioning for how versions and the changelog are set.
SDK repositories on GitLab or Bitbucket get their host's own CI files instead of these two.