-
Notifications
You must be signed in to change notification settings - Fork 6.2k
Closed as not planned
Labels
ciIssues related to ciIssues related to cienhancementSome improvement that isn't a featureSome improvement that isn't a feature
Milestone
Description
Problem
After we publish a release, we have to manually go to the code-server-aur repo and publish a new version of the package. This should be automated as part of the release process.
Solution
Add a job called aur
to publish.yaml
that waits on npm
and then publish new AUR package with script.
Notes
- this may not be straightforward. we'll need to add a CI account or something to the AUR package as a maintainer
- it could make sense for the job here to open a PR then have a separate GH Actions workflow in the actual repo that publishes the package on merge into default branch
- this could help: https://github.com/ouuan/AUR-template
Related
Metadata
Metadata
Assignees
Labels
ciIssues related to ciIssues related to cienhancementSome improvement that isn't a featureSome improvement that isn't a feature