Skip to content

[dev]: add aur job to publish.yaml #2845

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.

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

Closed
jsjoeio opened this issue Mar 8, 2021 · 5 comments
Closed

[dev]: add aur job to publish.yaml #2845

jsjoeio opened this issue Mar 8, 2021 · 5 comments
Labels
ci Issues related to ci enhancement Some improvement that isn't a feature
Milestone

Comments

@jsjoeio
Copy link
Contributor

jsjoeio commented Mar 8, 2021

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

@jsjoeio jsjoeio added the feature New user visible feature label Mar 8, 2021
@jsjoeio jsjoeio changed the title [dev]: add homebrew job to publish.yaml [dev]: add aur job to publish.yaml Mar 8, 2021
@jsjoeio jsjoeio added enhancement Some improvement that isn't a feature help-wanted and removed feature New user visible feature labels Mar 8, 2021
@jsjoeio jsjoeio added the chore Related to maintenance or clean up label May 14, 2021
@code-asher code-asher added ci Issues related to ci and removed chore Related to maintenance or clean up labels Oct 27, 2021
@code-asher code-asher added this to the Backlog milestone Oct 27, 2021
@stale
Copy link

stale bot commented Apr 25, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.

@stale stale bot added the stale label Apr 25, 2022
@jsjoeio
Copy link
Contributor Author

jsjoeio commented Apr 25, 2022

Still planning to do this

@stale stale bot removed the stale label Apr 25, 2022
@jsjoeio
Copy link
Contributor Author

jsjoeio commented Jul 19, 2022

I am hoping to work on this soon.

@jsjoeio
Copy link
Contributor Author

jsjoeio commented Jul 19, 2022

We could also create a PR into the code-server AUR repo and then publish to AUR on merge.

@jsjoeio
Copy link
Contributor Author

jsjoeio commented Aug 16, 2022

Closing in favor of #5366 and coder/code-server-aur#13

@jsjoeio jsjoeio closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Issues related to ci enhancement Some improvement that isn't a feature
Projects
None yet
Development

No branches or pull requests

2 participants