Ci by thumbrise · Pull Request #1 · thumbrise/otelext

thumbrise · 2026-03-17T18:25:45Z

CI/CD infrastructure for otelext

Bootstrap the project with CI quality gates and automated semantic versioning.

CI workflow (`ci.yml`) — runs on PRs to `main`

Three parallel jobs:

golangci — runs golangci-lint v2.4.0 with 80+ linters enabled, only reports new issues
test — runs unit tests and benchmarks across Go 1.25.x / 1.26.x matrix via go-task
commitlint — validates all PR commits follow Conventional Commits format

Release workflow (`release.yml`) — runs on push to `main` + manual dispatch

Runs semantic-release to automatically create GitHub releases with version bumps based on commit types:

feat → minor
fix / docs / chore → patch
BREAKING CHANGE → major
Includes workflow_dispatch trigger for manual recovery if release automation needs re-running.

Configuration files

File	Purpose
`.golangci.yaml`	Linter config — 80+ linters, relaxed rules for tests/handlers/middlewares
`.releaserc.json`	semantic-release config — commit analyzer rules, release notes generator with conventionalcommits preset
`.commitlintrc.json`	Commit message rules — requires type + subject, relaxed line length
`Taskfile.yaml`	Task runner — `test` (unit tests + benchmarks), `lint`
`.editorconfig`	4-space indent for JSON files

Node.js tooling

package.json declares devDependencies for commitlint and semantic-release. Both CI and Release workflows use npm ci with cache: npm for fast installs.

Temporary

stub.go — placeholder so Go toolchain has something to compile until real code is added.

Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>

…ease

…ntic-release, add dynamic branch for dry-run release

- Now cache key can be hashed with go.sum file. Optimization

…vents

Using base.ref (main) causes semantic-release to silently skip analysis because the current HEAD commit is not on main. Using head.ref (the PR branch) lets semantic-release actually process the commits.

…n release dry-run job Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>

thumbrise · 2026-03-17T21:05:45Z

logs of dry-run semantic-release:

Run npx semantic-release --branches "$BRANCH_REF" --dry-run
npm warn exec The following package was not found and will be installed: semantic-release@25.0.3
[9:03:11 PM] [semantic-release] › ℹ Running semantic-release version 25.0.3
[9:03:11 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/github"
[9:03:11 PM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[9:03:11 PM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[9:03:11 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/github"
[9:03:11 PM] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/github"
[9:03:11 PM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
[9:03:11 PM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
[9:03:11 PM] [semantic-release] › ℹ This run was triggered by a pull request and therefore a new version won't be published.

Need to recognize way to check possibility to guaranteed release version after merge PRs.
Now semantic-release skips with 0 exit code

BRANCH_REF was referenced but never set. Assign it from head.ref so semantic-release actually processes the PR branch commits instead of silently skipping because HEAD is not on main.

semantic-release refuses to analyze commits on PR branches, making the dry-run a no-op. Commitlint already validates commit messages (the main failure mode). Added workflow_dispatch to release.yml for manual recovery if release automation breaks on main.

github-actions · 2026-03-17T21:40:53Z

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

github-actions · 2026-03-17T21:56:31Z

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

github-actions · 2026-03-17T23:57:40Z

🎉 This PR is included in version 0.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

github-actions · 2026-03-18T00:13:26Z

🎉 This PR is included in version 0.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

thumbrise added 9 commits March 17, 2026 19:43

chore: Add .golangci.yaml, add basic Taskfile.yaml

28409e6

ci: Add golangci-lint.yml workflow

f91939b

ci: Add test.yml workflow

f581a9f

ci: Change name of test job

766b6b9

ci: Add commitlint workflow

12b1e82

ci: Add releaserc workflow

885e7a0

ci: Add releaserc dry run workflow

6182874

ci: Merge CI jobs in one workflow

f2718e9

ci: Replace golangci-lint action with official

425c84c

This comment was marked as resolved.

Sign in to view

fix: Adds flag dash to benchmark command in Taskfile

5b49578

Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>

This comment was marked as resolved.

Sign in to view

thumbrise added 5 commits March 17, 2026 23:29

chore: Add editorconfig

57ee669

ci: Add release rules to commit-analyzer

29ab54f

ci: Replace release workflow with official github action semantic-rel…

8476706

…ease

ci: Replace release DRY-RUN workflow with official github action sema…

dbc4a17

…ntic-release, add dynamic branch for dry-run release

ci: Replace commitlint job with official github action

24092b5

This comment was marked as resolved.

Sign in to view

thumbrise added 2 commits March 17, 2026 23:41

ci: Add package.json and lock for setup node github action

658f1ee

ci: Change order of checkout and setup go in test job

295c136

- Now cache key can be hashed with go.sum file. Optimization

This comment was marked as resolved.

Sign in to view

fix: Fix release dry-run to use correct branch ref for pull_request e…

58aff67

…vents

This comment was marked as resolved.

Sign in to view

fix(ci): use PR head branch for semantic-release dry-run

32f7c9e

Using base.ref (main) causes semantic-release to silently skip analysis because the current HEAD commit is not on main. Using head.ref (the PR branch) lets semantic-release actually process the commits.

This comment was marked as resolved.

Sign in to view

fix(ci): Replace interpolated head branch with $BRANCH_REF variable i…

8691c10

…n release dry-run job Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>

This comment was marked as resolved.

Sign in to view

fix(ci): define BRANCH_REF env var for semantic-release dry-run

aeadb16

BRANCH_REF was referenced but never set. Assign it from head.ref so semantic-release actually processes the PR branch commits instead of silently skipping because HEAD is not on main.

This comment was marked as resolved.

Sign in to view

thumbrise and others added 2 commits March 18, 2026 00:27

ci: Cache npm packages for workflows

110fce2

fix(ci): cache semantic-release plugins in release workflow

d81f849

thumbrise merged commit fe93b22 into main Mar 17, 2026
5 checks passed

github-actions Bot added the released label Mar 17, 2026

thumbrise deleted the ci branch March 18, 2026 00:14

Conversation

thumbrise commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

CI/CD infrastructure for otelext

CI workflow (ci.yml) — runs on PRs to main

Release workflow (release.yml) — runs on push to main + manual dispatch

Configuration files

Node.js tooling

Temporary

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

thumbrise commented Mar 17, 2026

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

Uh oh!

github-actions Bot commented Mar 17, 2026

Uh oh!

github-actions Bot commented Mar 17, 2026

Uh oh!

github-actions Bot commented Mar 17, 2026

Uh oh!

github-actions Bot commented Mar 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

thumbrise commented Mar 17, 2026 •

edited

Loading

CI workflow (`ci.yml`) — runs on PRs to `main`

Release workflow (`release.yml`) — runs on push to `main` + manual dispatch