Skip to content

Releasing

Jump to bottom
Phil Quitslund edited this page Nov 14, 2017 · 35 revisions

Creating a new release

From IntelliJ:

  • ensure that the changelog in resources/META-INF/plugin.xml is up-to-date (from the current milestone)
    • edit plugin.xml.template: update version number, release notes
    • run ant plugin.xml in a terminal emulator to update plugin.xml
  • commit these changes
  • in a terminal emulator, cd /project/root; ./build-all.sh
  • the plugin is created as flutter-studio.zip in /project/root/artifacts

From github:

From plugins.jetbrains.com:

Pushing a patch to an existing release

When it's necessary to patch a previously released build:

Create a branch

  • 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)

Cherry-pick the fix

  • cherrypick the specific commit (git cherry-pick 2d8ac6a)
  • rev the plugin numbers (append .1 to the plugin version in resources/META-INF/plugin.xml)
    • See details on editing under "Creating a new release", above
  • 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

Re-deploy the new Jar

Docs

Clone this wiki locally