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

Use same versioning scheme & release cadence as Prisma itself #93

Closed
schickling opened this issue Apr 9, 2020 · 2 comments · Fixed by #109
Closed

Use same versioning scheme & release cadence as Prisma itself #93

schickling opened this issue Apr 9, 2020 · 2 comments · Fixed by #109
Assignees
@divyenduz
Labels
kind/improvement An improvement to existing feature and code.
Milestone
Beta 6

Comments

@schickling
Copy link
Member

I suggest to adapt the same versioning scheme and release cadence as for Prisma itself.
@schickling schickling added the process/candidate Candidate for next Milestone. label Apr 9, 2020
@janpio janpio added the kind/improvement An improvement to existing feature and code. label Apr 9, 2020
@divyenduz divyenduz mentioned this issue Apr 20, 2020
Closed
@janpio janpio removed the process/candidate Candidate for next Milestone. label Apr 20, 2020
@janpio janpio added this to the Beta 3 milestone Apr 20, 2020
divyenduz pushed a commit that referenced this issue Apr 21, 2020
feat(alpha): via a new extension
6492b4b 
- Fixes #47
- Fixes #93

This PR is made against "alpha" and merging this should release a "new"
alpha extension.
@divyenduz divyenduz mentioned this issue Apr 21, 2020
Closed
divyenduz pushed a commit that referenced this issue Apr 21, 2020
feat(alpha): via a new extension
80c2a38 
- Fixes #47
- Fixes #93

This PR is made against "alpha" and merging this should release a "new"
alpha extension.
@janpio janpio modified the milestones: Beta 3, Beta 4 Apr 21, 2020
@divyenduz divyenduz mentioned this issue Apr 22, 2020
Merged
divyenduz pushed a commit that referenced this issue Apr 24, 2020
@janpio
feat(dev): via a new Prisma Dev extension (#109)
76c9b3d 
* feat(alpha): via a new extension

- Fixes #47
- Fixes #93

This PR is made against "alpha" and merging this should release a "new"
alpha extension.

* feat(alpha): incorporate release feedback

- Remove the alpha branch dependency
- Push only when bumping alpha
- Bump @prisma/* packages when updating package.json

* feat(alpha): use vsce show for extension version

* Update scripts/bump-sha.sh

Co-Authored-By: Jan Piotrowski <piotrowski+github@gmail.com>

* feat(dev): publish Prisma Dev as a new extension

- rename to dev
- merge with master, adjust bump deps
- add release-workflow.md

* Update release-workflow.md

Co-Authored-By: Jan Piotrowski <piotrowski+github@gmail.com>

* fix: job name

Fixes #82

Co-authored-by: Jan Piotrowski <piotrowski+github@gmail.com>
@divyenduz
Copy link

divyenduz commented Apr 24, 2020 •
edited
Loading

This is not possible right now because microsoft/vscode-vsce#148

image

Related:

@divyenduz divyenduz reopened this Apr 24, 2020
This was referenced Apr 24, 2020
Closed
Closed
@divyenduz divyenduz modified the milestones: Beta 4, Beta 5 May 4, 2020
@janpio janpio modified the milestones: Beta 5, Beta 6 May 12, 2020
@divyenduz
Copy link

This was implemented via #121

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

@divyenduz divyenduz

Labels
kind/improvement An improvement to existing feature and code.
Projects
None yet
Milestone
Beta 6
Development

Successfully merging a pull request may close this issue.

feat(dev): via a new Prisma Dev extension prisma/language-tools
3 participants
@janpio @divyenduz @schickling