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

Prevent Last Place of Launcher Semver from triggering mainnet CI #2306

Open
Akamig opened this issue Sep 6, 2023 · 1 comment
Open

Prevent Last Place of Launcher Semver from triggering mainnet CI #2306

Akamig opened this issue Sep 6, 2023 · 1 comment
Assignees
@Akamig
Labels
ci

Comments

@Akamig
Copy link
Member

Akamig commented Sep 6, 2023 •
edited
Loading

Issue

We could use last digit of launcher semver for internal testing purpose which does not trigger the release logic.
@Akamig Akamig added the ci label Sep 6, 2023
@Akamig Akamig self-assigned this Sep 6, 2023
@Akamig
Copy link
Member Author

Akamig commented Oct 4, 2023

Since we had talk about the testing environment of launcher in 09/27. this decision should be revised.

We can do this without noticeable risk, but 'how' we're going to use last digit need to be discussed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Akamig Akamig

Labels
ci
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Akamig