From bcfd7adb53ad7232936a19d6d5139af66f7472a2 Mon Sep 17 00:00:00 2001
From: Kamil Zyla <kamil@appsilon.com>
Date: Thu, 11 Jul 2024 11:33:13 +0200
Subject: [PATCH 1/2] chore: prepare the package for further development

1. Add a new version to pkgdown/versions.yml.
2. Set a development version in DESCRIPTION.
3. Update NEWS.md.
---
 DESCRIPTION          |  2 +-
 NEWS.md              | 10 +++++++---
 pkgdown/versions.yml |  5 ++++-
 3 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/DESCRIPTION b/DESCRIPTION
index ecc69e8d..efafee12 100644
--- a/DESCRIPTION
+++ b/DESCRIPTION
@@ -1,6 +1,6 @@
 Package: rhino
 Title: A Framework for Enterprise Shiny Applications
-Version: 1.9.0
+Version: 1.9.0.9000
 Authors@R:
   c(
     person("Kamil", "Żyła", role = c("aut", "cre"), email = "opensource+kamil@appsilon.com"),
diff --git a/NEWS.md b/NEWS.md
index 4839b4e0..b108da0e 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,4 +1,8 @@
-# rhino 1.9.0
+# rhino (development version)
+
+# [rhino 1.9.0](https://github.com/Appsilon/rhino/releases/tag/v1.9.0)
+
+See _[How-to: Rhino 1.9 Migration Guide](https://appsilon.github.io/rhino/articles/how-to/migrate-1-9.html)_
 
 1. Added `sass: custom` configuration option for cleaner integration with `bslib`.
 2. Introduced `format_js()` and `format_sass()` powered by [prettier](https://prettier.io).
@@ -8,11 +12,11 @@
 
 # [rhino 1.8.0](https://github.com/Appsilon/rhino/releases/tag/v1.8.0)
 
+See _[How-to: Rhino 1.8 Migration Guide](https://appsilon.github.io/rhino/articles/how-to/migrate-1-8.html)_
+
 1. All linter functions migrated to `box.linters`. New rhino projects will be configured to use linters from `box.linters`.
 2. Updated GitHub Workflow template triggers.
 
-See _[How-to: Rhino 1.8 Migration Guide](https://appsilon.github.io/rhino/articles/how-to/migrate-1-8.html)_
-
 # [rhino 1.7.0](https://github.com/Appsilon/rhino/releases/tag/v1.7.0)
 
 See _[How-to: Rhino 1.7 Migration Guide](https://appsilon.github.io/rhino/articles/how-to/migrate-1-7.html)_
diff --git a/pkgdown/versions.yml b/pkgdown/versions.yml
index 5c69b45b..270a6f3d 100644
--- a/pkgdown/versions.yml
+++ b/pkgdown/versions.yml
@@ -1,8 +1,11 @@
 - git_ref: 'refs/remotes/origin/main'
   url: /dev
   label: true
-- git_ref: 'refs/tags/v1.8.0'
+- git_ref: 'refs/tags/v1.9.0'
   url: '/'
+  label: '1.9'
+- git_ref: 'refs/tags/v1.8.0'
+  url: '/v1.8.0'
   label: '1.8'
 - git_ref: 'refs/tags/v1.7.0'
   url: '/v1.7.0'

From c64e79295c2c50a23d0daa2edbc4e0a4ed1c5427 Mon Sep 17 00:00:00 2001
From: Kamil Zyla <kamil@appsilon.com>
Date: Thu, 11 Jul 2024 11:41:03 +0200
Subject: [PATCH 2/2] docs: update release instructions - complete showcase
 upgrade

---
 .github/CONTRIBUTING.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 812715d5..cc575da8 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -121,6 +121,7 @@ Use `rc.2`, `rc.3` and so on for subsequent submissions.
         * Link the `# rhino X.Y.Z` header to the GitHub release.
         * Add a link to the migration guide in `NEWS.md`.
 3. Announce the release on `#proj-rhino`.
+4. Complete the upgrade of Rhino Showcase.
 
 ## Development process