From 037972483cf46cb0d09ca7cd897b0f0e72d67d20 Mon Sep 17 00:00:00 2001 From: mavnn Date: Tue, 18 Dec 2018 11:57:45 +0000 Subject: [PATCH] The current deploy instructions don't work as master is a protected branch. --- README.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 10f522c1..b3bcb01f 100644 --- a/README.md +++ b/README.md @@ -4,10 +4,7 @@ UI widgets we use. ## Dual publishing notes -This package is published for both 0.18 and 0.19! The 0.18 source code is in src-0.18. While -we still have codebases that utilize either version we'll need to make updates to any version -after 6.0.0 in both src and src-0.18. Eventually, everything will be updated to 0.19 at which -point we will delete src-0.18 and stop publishing for Elm 0.18. +All internal consumers of this repository have been upgrade to Elm 0.19, so we will not be continuing to update the Elm 0.18 source. ## Versioning policy @@ -76,13 +73,19 @@ You can run this locally to catch errors before you push! Once your PR is merged, you can publish `master` as a new version: -Run the following to bump && publish the version in `elm-packages.json`: +Run the following to bump && publish the version in `elm.json`: + +``` +elm bump +``` + +Commit and push your changes in a PR. Once it's approved and merged, +then: ``` -elm-package bump git tag -a 5.10.0 -m "release version 5.10.0" git push origin master --tags -elm-package publish +elm publish ``` You can also add a tag in https://github.com/NoRedInk/noredink-ui/releases/new if you want to add more detail.