guptarohit / asciigraph / 22818678271
95%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 5
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 95.137%. Remained the same
22818678271

push

github

web-flow 
ci(release): automate versioning and publishing (#72)

### Summary
Automates the release flow with release-please for versioning/changelog
management and GoReleaser for publishing assets.
This removes manual tag creation from the normal release path, keeps
CHANGELOG.md as the source of truth, and adds checks around release
metadata and PR titles.

### What Changed
- added release-please configuration
  - release-please-config.json
  - .release-please-manifest.json
- added a new Release Please workflow to:
  - open/update release PRs on master
  - create the release/tag when the release PR is merged
  - run GoReleaser to publish release assets
- repurposed the old tag-driven release workflow into a manual recovery
workflow for republishing assets for an existing tag
- added PR title linting for Conventional Commit style PR titles
- added CONTRIBUTING.md guidance for:
  - PR title format
  - release/versioning expectations
  - maintainer merge guidance
- added goreleaser check to CI
- modernized .goreleaser.yml for GoReleaser v2
  - added version: 2
  - migrated archive config to formats
  - migrated Docker publishing to dockers_v2
  - removed the broken windows/arm build target
  - updated goreleaser.dockerfile for dockers_v2 platform-aware copying

### New Release Flow
1. PRs merge into master
2. release-please opens or updates a release PR
3. the release PR updates CHANGELOG.md and proposes the next version
4. merging the release PR creates the tag/release
5. GoReleaser publishes binaries, checksums, and container images

### Notes
- CHANGELOG.md remains the canonical release notes source
- contributors only need Conventional Commit style PR titles; individual
commit messages are optional
- maintainers should keep merge commit titles aligned with PR titles if
merge commits are used, so release automation can infer versions
correctly

### Testing
- ran go test ./...
- ran goreleaser check
- CI passes on this branch

450 of 473 relevant lines covered (95.14%)

1717.81 hits per line

Jobs
ID Job ID Ran Files Coverage
1 Go- - 22818678271.1 5
95.14
 GitHub Action Run
Source Files on build 22818678271