JAForbes/pr-release

Issues

• Log open handles when process should be exiting.

  #358 opened 2 years ago by JAForbes
  0

• npx pr-release actions-yml is a no-op in some environments

  #357 opened 2 years ago by JAForbes
  0

• Mismatch between Quick Start in readme and website

  #356 opened 2 years ago by qgustavor
  6

• Default branch naming scheme

  #349 opened 3 years ago by pygy
  5

• Add more documentation about multiple release channel approaches

  #348 opened 3 years ago by JAForbes
  2

• Ensure package.version is in sync with release version in merge workflow

  #278 opened 3 years ago by JAForbes
  0

• HTML in PR description can be truncated in change description

  #306 opened 3 years ago by JAForbes
  0

• Document alternative branching conventions for different development styles

  #353 opened 3 years ago by JAForbes
  0

• Provide a way to have PR skip the change log (a dedicated label ?)

  #350 opened 3 years ago by pygy
  2

• Documention headings do not have anchors

  #335 opened 3 years ago by JAForbes
  0

• While juggling release channels, how do we ensure the change log ends up in the right repo?

  #347 opened 3 years ago by pygy
  2

• The prerelases published on each PR merge don't match the future version

  #345 opened 3 years ago by pygy
  3

• Should run tests in merge.yml/pr.yml to prevent publishing with failed tests.

  #334 opened 3 years ago by JAForbes
  0

• pr-release should use prerelease in CI

  #333 opened 3 years ago by JAForbes
  1

• Title doesn't always change on patch PR description

  #313 opened 3 years ago by JAForbes
  0

• Vanity semver mode

  #330 opened 3 years ago by JAForbes
  0

• infer-prerelease assumes package already exists

  #326 opened 3 years ago by JAForbes
  0

• Release title doesn't update with new versions (body does)

  #327 opened 3 years ago by JAForbes
  0

• Merge command doesn't handle no existing PR with long commit history.

  #323 opened 3 years ago by JAForbes
  0

• Maintain sqlite db per repo and query the sqlite state instead of the API

  #322 opened 3 years ago by JAForbes
  0

• If no prior release PR, pr-release includes all PRs ever

  #307 opened 3 years ago by JAForbes
  0

• Special case dependabot

  #305 opened 3 years ago by JAForbes
  0

• Optionally enforce semver label

  #304 opened 3 years ago by JAForbes
  0

• Rollback release text is formatted as code unintentionally

  #302 opened 3 years ago by JAForbes
  0

• Sometimes after a rollback the generated release revsion is vnull...

  #299 opened 3 years ago by JAForbes
  0

• pre-release automatically being created on merge of next->main

  #298 opened 3 years ago by JAForbes
  0

• Support custom npm registries

  #297 opened 3 years ago by JAForbes
  0

• Should handle forks gracefully

  #293 opened 3 years ago by JAForbes
  0

• --out not respected in merge command

  #294 opened 3 years ago by JAForbes
  0

• pr-release should be a github app to avoid incorrect contributor assignment

  #292 opened 3 years ago by JAForbes
  1

• Strip headers and todos from change description

  #289 opened 3 years ago by JAForbes
  0

• Should pr-release publish its own package on a delay?

  #288 opened 3 years ago by JAForbes
  0

• HTML comment handling

  #285 opened 3 years ago by JAForbes
  0

• Uncommenting the template has the wrong dedent

  #282 opened 3 years ago by JAForbes
  1

• Concurrent CI pipelines can lead to failed npm publishes for pre-releases

  #265 opened 3 years ago by JAForbes
  2

• Document rollback feature on website

  #281 opened 3 years ago by JAForbes
  0

• Should release in previous release PR should take precedence over package.json?

  #277 opened 3 years ago by JAForbes
  1

• FAQ on how to configure tests on every release

  #276 opened 3 years ago by JAForbes
  0

• Document that admins should not be included for branch protection

  #275 opened 3 years ago by JAForbes
  0

• Document that GH_TOKEN has to include all repo permissions and workflow permissions

  #274 opened 3 years ago by JAForbes
  0

• Pushing straight to next on pr-release first run leads to a crash

  #271 opened 3 years ago by JAForbes
  0

• Use pr-release in some real projects.

  #226 opened 3 years ago by JAForbes
  1

• Release PR description generation doesn't handle headings well

  #268 opened 3 years ago by JAForbes
  0

• repairTarget fails on protected branch

  #262 opened 3 years ago by JAForbes
  0

• docs say to configure GITHUB_TOKEN but that is impossible

  #234 opened 3 years ago by JAForbes
  1

• PR description update bug

  #248 opened 3 years ago by JAForbes
  0

• Make version infer include tag/channel

  #243 opened 3 years ago by JAForbes
  1

• Largest release version not being used

  #249 opened 3 years ago by JAForbes
  1

• actions-yml does not work in other repos

  #231 opened 3 years ago by JAForbes
  0

• Auto feature PR generation can have wrong author.

  #225 opened 3 years ago by JAForbes
  0