Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve release publishing workflow #162

Open
phlax opened this issue Jan 7, 2022 · 0 comments · May be fixed by #163
Open

Improve release publishing workflow #162

phlax opened this issue Jan 7, 2022 · 0 comments · May be fixed by #163
Milestone
General repo clea...

Comments

@phlax
Copy link
Member

phlax commented Jan 7, 2022 •
edited
Loading

Currently we manually create releases and any package that is not marked -dev in its VERSION file gets published

This creates a lot of unwanted commits, and boilerplate tasks that are pretty annoying and potentially unnecessary.

One possible solution is to make it such that:

  • When a PR lands on main if the -dev version has changed for one or more packages...
  • CI creates a branch for a new release, updates the VERSION files and publishes the packages to the version indicated by the previous dev version/s
@phlax phlax linked a pull request Jan 7, 2022 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
General repo cleanups/improvements/te...
Development

Successfully merging a pull request may close this issue.

[WIP] release: Improve publishing pipeline phlax/toolshed
1 participant
@phlax