Merge pull request #5375 from opsmill/dga-20250105-rn-1.1.1

Prepare release 1.1.1
opsmill · Jan 6, 2025 · ebf95c2 · ebf95c2
2 parents 4032461 + aecc5d2
commit ebf95c2
Show file tree

Hide file tree

Showing 11 changed files with 104 additions and 10 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -11,6 +11,15 @@ This project uses [*towncrier*](https://towncrier.readthedocs.io/) and the chang
 
 <!-- towncrier release notes start -->
 
+## [Infrahub - v1.1.1](https://github.com/opsmill/infrahub/tree/infrahub-v1.1.1) - 2025-01-05
+
+### Fixed
+
+- Raise a better error when trying to resolve an invalid HFID for a relationship ([#5360](https://github.com/opsmill/infrahub/issues/5360))
+- Fix an issue with session management that could lead to the crash of the GraphQL resolver
+- Fix query response time when the number of historical value for a given attribute is large
+- Fixed an issue that prevented using an IP Namespace on a branch
+
 ## [Infrahub - v1.1.0](https://github.com/opsmill/infrahub/tree/infrahub-v1.1.0) - 2024-12-30
 
 ### Removed

diff --git a/changelog/+attrquery.fixed.md b/changelog/+attrquery.fixed.md
diff --git a/changelog/+gqlquery.fixed.md b/changelog/+gqlquery.fixed.md
diff --git a/changelog/+ipnamespace-branch.fixed.md b/changelog/+ipnamespace-branch.fixed.md
diff --git a/changelog/5360.fixed.md b/changelog/5360.fixed.md
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -205,7 +205,7 @@ services:
       retries: 5
 
   infrahub-server:
-    image: "${INFRAHUB_DOCKER_IMAGE:-registry.opsmill.io/opsmill/infrahub}:${VERSION:-1.1.0}"
+    image: "${INFRAHUB_DOCKER_IMAGE:-registry.opsmill.io/opsmill/infrahub}:${VERSION:-1.1.1}"
     restart: unless-stopped
     command: >
       gunicorn --config backend/infrahub/serve/gunicorn_config.py
@@ -251,7 +251,7 @@ services:
     deploy:
       mode: replicated
       replicas: 2
-    image: "${INFRAHUB_DOCKER_IMAGE:-registry.opsmill.io/opsmill/infrahub}:${VERSION:-1.1.0}"
+    image: "${INFRAHUB_DOCKER_IMAGE:-registry.opsmill.io/opsmill/infrahub}:${VERSION:-1.1.1}"
     command: prefect worker start --type infrahubasync --pool infrahub-worker --with-healthcheck
     restart: unless-stopped
     depends_on:

diff --git a/docs/docs/release-notes/infrahub/release-1_1_1.mdx b/docs/docs/release-notes/infrahub/release-1_1_1.mdx
@@ -0,0 +1,88 @@
+---
+title: Release 1.1.1
+---
+<table>
+  <tbody>
+    <tr>
+      <th>Release Number</th>
+      <td>1.1.1</td>
+    </tr>
+    <tr>
+      <th>Release Date</th>
+      <td>January 5th, 2025</td>
+    </tr>
+    <tr>
+      <th>Release Codename</th>
+      <td>Lyon, Patch #1</td>
+    </tr>
+    <tr>
+      <th>Tag</th>
+      <td>[infrahub-v1.1.1](https://github.com/opsmill/infrahub/releases/tag/infrahub-v1.1.1)</td>
+    </tr>
+  </tbody>
+</table>
+
+# Release 1.1.1
+
+This release is a bug-fix release to resolve issues found in Infrahub v1.1.0 and prior.
+
+## Main changes
+
+The complete list of changes can always be found in the `CHANGELOG.md` file in the Infrahub Git repository.
+
+### Fixed
+
+- Raise a better error when trying to resolve an invalid HFID for a relationship ([#5360](https://github.com/opsmill/infrahub/issues/5360))
+- Fix an issue with session management that could lead to the crash of the GraphQL resolver
+- Fix query response time when the number of historical value for a given attribute is large
+- Fixed an issue that prevented using an IP Namespace on a branch
+
+## 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 `VERSION` environment variable and relaunch:
+  - `export VERSION="1.1.1"; 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.
diff --git a/docs/sidebars.ts b/docs/sidebars.ts
@@ -315,6 +315,7 @@ const sidebars: SidebarsConfig = {
             slug: 'release-notes/infrahub',
           },
           items: [
+            'release-notes/infrahub/release-1_1_1',
             'release-notes/infrahub/release-1_1_0',
             'release-notes/infrahub/release-1_0_10',
             'release-notes/infrahub/release-1_0_9',

diff --git a/helm/Chart.yaml b/helm/Chart.yaml
@@ -15,12 +15,12 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 4.1.0
+version: 4.1.1
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "1.1.0"
+appVersion: "1.1.1"
 
 dependencies:
   - name: neo4j

diff --git a/pyproject.toml b/pyproject.toml
@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "infrahub-server"
-version = "1.1.0"
+version = "1.1.1"
 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"

diff --git a/python_testcontainers/pyproject.toml b/python_testcontainers/pyproject.toml
@@ -1,6 +1,6 @@
 [project]
 name = "infrahub-testcontainers"
-version = "1.1.0"
+version = "1.1.1"
 requires-python = ">=3.9"
 
 [tool.poetry]