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

Bump project version #565

Merged
merged 1 commit into from
Feb 5, 2015
Merged

Bump project version #565

merged 1 commit into from
Feb 5, 2015

Conversation

Martii
Copy link
Member

@Martii Martii commented Feb 5, 2015

Martii added a commit that referenced this pull request Feb 5, 2015
@Martii
Merge pull request #565 from Martii/bumpProjectVersion
4f6511e 
Bump project version

Auto-merge
@Martii Martii merged commit 4f6511e into OpenUserJS:master Feb 5, 2015
@Martii Martii deleted the bumpProjectVersion branch February 5, 2015 18:35
@Martii Martii added CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. migration Use this to indicate that it may apply to an existing or announced migration. labels Feb 5, 2015
@Martii
Copy link
Member Author

Martii commented Feb 5, 2015

Nodejitsu isn't paying any attention to this again on snapshot creation... e.g. version on pro showing will probably be 0.1.6-51 instead of the correct 0.1.7 ... this might self correct at some point but keeping dev at this... henceforth another reason for #425

@Martii
Copy link
Member Author

Martii commented Feb 5, 2015

Attempting -r 0.1.7 on deploy to force the version switch. Repeated failed attempts (-52 and -53) to have nodejitsu auto read in existing and current semver version name... this might work... will update this comments status... there's no guarantee that their backend will keep this but I'll deploy twice to see here and we can pray... 0.1.7 deployed and active... deploying 0.1.7-1... appears to be successful... what a nightmare... @sizzlemctwizzle please consider that new provider soon. Thanks.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. migration Use this to indicate that it may apply to an existing or announced migration.
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Martii