Source GitHub Release description from CHANGELOG.md

Aperta
#268 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@galargh ci sta già lavorando.

Dal 15/5/2023.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

dif/medium P3

Currently we use Unified CI for tagging releases based on version.json, but we'd like to minimize the effort for cutting releases so that we can cut them more frequently.

So I propose we instead cut releases using https://github.com/pl-strflt/changelog-driven-release. Basically the workflow would look like:

  • Accumulate changes in the [Unreleased] section of the CHANGELOG
    • These should be added as commits are added, and the CHANGELOG update should happen as part of the PR for a feature
  • When ready to release, change [Unreleased] to [vX.Y.Z] YYYY-mm-dd, which is then detected by CI as a release and results in a new tag and a GitHub release with the changelog contents in the release notes.

Other requirements:

  • We currently run Kubo tests for each release, until enough are moved into Boxo, so we need to run releases on a release-vX.Y.Z branch and merge into release which should trigger the release. This way we don't have to "freeze" main while we do a release. Once the release is complete, merge release into main (which should NOT trigger a release). This is different than most folks, who just merge to main which triggers a release based on the tip of main...we do NOT want this behavior.
  • We love all the checks that Unified CI does for releases and would like to keep them (release checker workflow, which runs gorelease et al to verify the release version, call out breaking changes, etc.)
Lingua principale
Go
Stelle
326
Fork
165
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ipfs/boxo

Tutte le issue di ipfs/boxo

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.