Skip to content

Should beta releases be published automatically on each merge to main? #151

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

Open
nrayburn-tech opened this issue Apr 16, 2025 · 2 comments
Assignees

Comments

@nrayburn-tech
Copy link
Collaborator

Right now, each merge to main creates a draft release. This isn't available to users, although they could go to the GitHub action and manually download the plugin and install it.

  1. Should this process be changed to instead create a GitHub "pre-release" that can be viewed/downloaded by users?
  2. Should this process be changed to automatically publish to a pre-release plugin channel that users can download from if they want to?

The goal here is just to allow users to easily test the latest changes without a full release.

Ref: #126 (comment)

@dr460nf1r3
Copy link

Sounds good to me!

@nrayburn-tech nrayburn-tech self-assigned this Apr 19, 2025
@nrayburn-tech
Copy link
Collaborator Author

For now, the easiest way to get the most recent changes that are in the main branch and not yet published to the marketplace is to download the zip artifact from the most recent successful build https://github.com/oxc-project/oxc-intellij-plugin/actions/workflows/build.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants