Release 1.0.3 prep (#4895)

CHANGELOG.md

@@ -11,6 +11,14 @@ This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the chang
 
 <!-- towncrier release notes start -->
 
+## [1.0.3](https://github.com/opsmill/infrahub/tree/v1.0.2) - 2024-11-08
+
+### Fixed
+
+- Fix hierarchical schema update logic to correctly update peer on parent relationship of new node ([#4838](https://github.com/opsmill/infrahub/issues/4838))
+- Fix hierarchical schema update logic to correctly update peer on parent of new child node ([#4839](https://github.com/opsmill/infrahub/issues/4839))
+- Define the version of numpy to install in pyproject.toml
+
 ## [1.0.2](https://github.com/opsmill/infrahub/tree/v1.0.2) - 2024-11-06
 
 ### Fixed

docs/docs/release-notes/infrahub/release-1_0_3.mdx

@@ -0,0 +1,87 @@
+---
+title: Release 1.0.3
+---
+<table>
+  <tbody>
+    <tr>
+      <th>Release Number</th>
+      <td>1.0.3</td>
+    </tr>
+    <tr>
+      <th>Release Date</th>
+      <td>November 8th, 2024</td>
+    </tr>
+    <tr>
+      <th>Release Codename</th>
+      <td>Stockholm, Patch #3</td>
+    </tr>
+    <tr>
+      <th>Tag</th>
+      <td>[infrahub-v1.0.3](https://github.com/opsmill/infrahub/releases/tag/infrahub-v1.0.3)</td>
+    </tr>
+  </tbody>
+</table>
+
+# Release 1.0.3
+
+This is a bug-fix release to address issues found in Infrahub v1.0.2.
+
+## Main changes
+
+The complete list of changes can always be found in the `CHANGELOG.md` file in the Infrahub Git repository.
+
+### Fixed
+
+- Fix hierarchical schema update logic to correctly update peer on parent relationship of new node ([#4838](https://github.com/opsmill/infrahub/issues/4838))
+- Fix hierarchical schema update logic to correctly update peer on parent of new child node ([#4839](https://github.com/opsmill/infrahub/issues/4839))
+- Define the version of numpy to install in pyproject.toml
+
+## Migration guide
+
+The process to migrate your instance of Infrahub to the latest version may vary depending on your deployment of Infrahub.
+However, at a high-level, it will involve getting the latest version of the Infrahub code, and then performing any needed Database Migrations and Schema updates.
+
+Please ensure you have a **backup of your Infrahub environment** prior to attempting any migration or upgrade activities.
+
+### Migration of an Infrahub instance
+
+**First**, update the Infrahub version running in your environment.
+
+Below are some example ways to get the latest version of Infrahub in your environment.
+
+- For deployments via Docker Compose, update your container version by updating the `IMAGE_VER` environment variable and relaunch:
+  - `export VERSION="1.0.3"; docker compose pull && docker compose up -d`
+- For deployments via Kubernetes, utilize the latest version of the Helm chart supplied with this release
+
+**Second**, once you have gotten the desired version of Infrahub in your environment, please run the following commands.
+
+> Note: If you are running Infrahub in Docker/K8s, these commands need to run from a container where Infrahub is installed.
+
+```shell
+infrahub db migrate
+infrahub db update-core-schema
+```
+
+**Finally**, restart all instances of Infrahub.
+
+### Migration of a dev or demo instance
+
+If you are using the `dev` or `demo` environments, we have provided `invoke` commands to aid in the migration to the latest version.
+The below examples provide the `demo` version of the commands, however similar commands can be used for `dev` as well.
+
+```shell
+invoke demo.stop
+invoke demo.build
+invoke demo.migrate
+invoke demo.start
+```
+
+If you don't want to keep your data, you can start a clean instance with the following command.
+
+> **Warning: All data will be lost, please make sure to backup everything you need before running this command.**
+
+```shell
+invoke demo.destroy demo.build demo.start demo.load-infra-schema demo.load-infra-data
+```
+
+The repository https://github.com/opsmill/infrahub-demo-edge has also been updated, it's recommended to pull the latest changes into your fork.

docs/docs/release-notes/infrahub/release-1_0_3-DRAFT.mdx → docs/docs/release-notes/infrahub/release-1_0_4-DRAFT.mdx

@@ -1,5 +1,5 @@
 ---
-title: Release 1.0.3 - DEVELOPMENT
+title: Release 1.0.4 - DEVELOPMENT
 ---
 <table>
   <tbody>
@@ -22,7 +22,7 @@ title: Release 1.0.3 - DEVELOPMENT
   </tbody>
 </table>
 
-# Release 1.0.3
+# Release 1.0.4
 
 ## Main changes
 
@@ -48,7 +48,7 @@ Please ensure you have a **backup of your Infrahub environment** prior to attemp
 Below are some example ways to get the latest version of Infrahub in your environment.
 
 - For deployments via Docker Compose, update your container version by updating the `IMAGE_VER` environment variable and relaunch:
-  - `export VERSION="1.0.3"; docker compose pull && docker compose up -d`
+  - `export VERSION="1.0.4"; docker compose pull && docker compose up -d`
 - For deployments via Kubernetes, utilize the latest version of the Helm chart supplied with this release
 
 **Second**, once you have gotten the desired version of Infrahub in your environment, please run the following commands.

docs/sidebars.ts

@@ -311,7 +311,8 @@ const sidebars: SidebarsConfig = {
             slug: 'release-notes/infrahub',
           },
           items: [
-            // 'release-notes/infrahub/release-1_0_3-DRAFT',
+            // 'release-notes/infrahub/release-1_0_4-DRAFT'
+            'release-notes/infrahub/release-1_0_3',
             'release-notes/infrahub/release-1_0_2',
             'release-notes/infrahub/release-1_0_1',
             'release-notes/infrahub/release-1_0',

pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "infrahub-server"
-version = "1.0.2"
+version = "1.0.3"
 description = "Infrahub is taking a new approach to Infrastructure Management by providing a new generation of datastore to organize and control all the data that defines how an infrastructure should run."
 authors = ["OpsMill <[email protected]>"]
 readme = "README.md"