From 7513bda9892e80f978f7d0da7358e47b1c846133 Mon Sep 17 00:00:00 2001 From: Brett Lykins Date: Fri, 8 Nov 2024 10:34:24 -0500 Subject: [PATCH] Release 1.0.3 prep (#4895) --- CHANGELOG.md | 8 ++ changelog/+numpy.fixed.md | 1 - changelog/4838.fixed.md | 1 - changelog/4839.fixed.md | 1 - .../release-notes/infrahub/release-1_0_3.mdx | 87 +++++++++++++++++++ ..._0_3-DRAFT.mdx => release-1_0_4-DRAFT.mdx} | 6 +- docs/sidebars.ts | 3 +- pyproject.toml | 2 +- 8 files changed, 101 insertions(+), 8 deletions(-) delete mode 100644 changelog/+numpy.fixed.md delete mode 100644 changelog/4838.fixed.md delete mode 100644 changelog/4839.fixed.md create mode 100644 docs/docs/release-notes/infrahub/release-1_0_3.mdx rename docs/docs/release-notes/infrahub/{release-1_0_3-DRAFT.mdx => release-1_0_4-DRAFT.mdx} (95%) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9359910761..d80c7268b6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,14 @@ This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the chang +## [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 diff --git a/changelog/+numpy.fixed.md b/changelog/+numpy.fixed.md deleted file mode 100644 index 23b517d529..0000000000 --- a/changelog/+numpy.fixed.md +++ /dev/null @@ -1 +0,0 @@ -Define the version of numpy to install in pyproject.toml \ No newline at end of file diff --git a/changelog/4838.fixed.md b/changelog/4838.fixed.md deleted file mode 100644 index b5673887ed..0000000000 --- a/changelog/4838.fixed.md +++ /dev/null @@ -1 +0,0 @@ -Fix hierarchical schema update logic to correctly update peer on parent relationship of new node \ No newline at end of file diff --git a/changelog/4839.fixed.md b/changelog/4839.fixed.md deleted file mode 100644 index d18670ff6d..0000000000 --- a/changelog/4839.fixed.md +++ /dev/null @@ -1 +0,0 @@ -Fix hierarchical schema update logic to correctly update peer on parent of new child node \ No newline at end of file diff --git a/docs/docs/release-notes/infrahub/release-1_0_3.mdx b/docs/docs/release-notes/infrahub/release-1_0_3.mdx new file mode 100644 index 0000000000..3a0d7320a9 --- /dev/null +++ b/docs/docs/release-notes/infrahub/release-1_0_3.mdx @@ -0,0 +1,87 @@ +--- +title: Release 1.0.3 +--- + + + + + + + + + + + + + + + + + + + +
Release Number1.0.3
Release DateNovember 8th, 2024
Release CodenameStockholm, Patch #3
Tag[infrahub-v1.0.3](https://github.com/opsmill/infrahub/releases/tag/infrahub-v1.0.3)
+ +# 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. \ No newline at end of file diff --git a/docs/docs/release-notes/infrahub/release-1_0_3-DRAFT.mdx b/docs/docs/release-notes/infrahub/release-1_0_4-DRAFT.mdx similarity index 95% rename from docs/docs/release-notes/infrahub/release-1_0_3-DRAFT.mdx rename to docs/docs/release-notes/infrahub/release-1_0_4-DRAFT.mdx index 892d155784..e1d5593f99 100644 --- a/docs/docs/release-notes/infrahub/release-1_0_3-DRAFT.mdx +++ b/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 --- @@ -22,7 +22,7 @@ title: Release 1.0.3 - DEVELOPMENT
-# 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. diff --git a/docs/sidebars.ts b/docs/sidebars.ts index 82409c6f4d..622aedb32e 100644 --- a/docs/sidebars.ts +++ b/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', diff --git a/pyproject.toml b/pyproject.toml index b5397bfddf..574d17e1bc 100644 --- a/pyproject.toml +++ b/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 "] readme = "README.md"