Prepare release: 1.1.1 (#183)

* Prepare release 1.1.1 Workflow: Release stage 1 - create release PR, run: 27 * fixed changes.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Tim Pillinger <[email protected]>
cylc · Sep 14, 2022 · 0a13dde · 0a13dde
1 parent c596df3
commit 0a13dde
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 5 deletions.
diff --git a/CHANGES.md b/CHANGES.md
@@ -5,13 +5,15 @@ creating a new release entry be sure to copy & paste the span tag with the
 `actions:bind` attribute, which is used by a regex to find the text to be
 updated. Only the first match gets replaced, so it's fine to leave the old
 ones in. -->
-## __cylc-rose-1.1.1 (<span actions:bind='release-date'>Upcoming</span>)__
+## __cylc-rose-1.1.1 (<span actions:bind='release-date'>Released 2022-09-14</span>)__
 
 ### Fixes
 
 [#171](https://github.com/cylc/cylc-rose/pull/171) - Fix bug where Cylc Rose
 passed `rose-suite.conf` items commented with `!` or `!!` to Cylc regardless.
 
+[#172](https://github.com/cylc/cylc-rose/pull/172) - Allow getting a workflow
+name when source is not an SVN repo.
 
 ## __cylc-rose-1.1.0 (<span actions:bind='release-date'>Released 2022-07-28</span>)__
 
@@ -30,9 +32,6 @@ a database locking issue with the `rose_prune` built-in app.
 
 ### Fixes
 
-[#172](https://github.com/cylc/cylc-rose/pull/172) - Allow getting a workflow
-name when source is not an SVN repo.
-
 [#139](https://github.com/cylc/cylc-rose/pull/139) - Make `rose stem` command
 work correctly with changes made to `cylc install` in
 [cylc-flow PR #4823](https://github.com/cylc/cylc-flow/pull/4823)

diff --git a/cylc/rose/__init__.py b/cylc/rose/__init__.py
@@ -205,4 +205,4 @@
 
 """
 
-__version__ = '1.1.1.dev'
+__version__ = '1.1.1'