-
Notifications
You must be signed in to change notification settings - Fork 326
Releasing
Devon Carew edited this page Jul 24, 2017
·
35 revisions
- ensure that the changelog in plugin.xml is up-to-date (from the current milestone)
- commit these changes
- from the menu, choose Build > Prepare plugin module for deployment
- the plugin file created as
flutter-intellij.jar
in the project root
- go to https://github.com/flutter/flutter-intellij/releases
- select
Draft a new release
- enter a version tag and release title of
x.y.z
(e.g.,12.0
)
- sign into https://plugins.jetbrains.com
- from https://plugins.jetbrains.com/plugin/9212?pr=idea, select
'update plugin'
- upload the
flutter-intellij.jar
created from the earlier step
When it's necessary to patch a previously released build:
- the fix should have already been committed to master
- look at the releases page and get the git commit of the release to patch
- create a new branch locally from that commit (
git branch release_15.0 4324f80
) - change to that branch (
git checkout release_15.0
)
- cherrypick the specific commit (
git cherry-pick 2d8ac6a
) - rev the plugin numbers (append
.1
to the plugin version inresources/META-INF/plugin.xml
) - commit your version change and push the new branch up to the repo
- if on a fork of the main repo, please make sure to push to the main repo:
git push upstream release_15.0
- if the branch already exists on the upstream repo, use
git checkout -b release_15.0 upstream/release_15.0
to get a local copy
- if on a fork of the main repo, please make sure to push to the main repo:
- build a new version of the jar file (from the menu, choose Build > Prepare plugin module for deployment)
- sign into https://plugins.jetbrains.com
- from https://plugins.jetbrains.com/plugin/9212?pr=idea, select
'update plugin'
- upload the
flutter-intellij.jar
created from the earlier step