Skip to content

Commit 5e07e44

Browse files
committed
Add changelog for Self-Hosted v2.1.0 release
1 parent e88ab81 commit 5e07e44

File tree

2 files changed

+20
-0
lines changed

2 files changed

+20
-0
lines changed

docs/product/administration/changelog.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,25 @@ description: Find out about the latest changes to the Self-Hosted Spacelift.
44

55
# Changelog
66

7+
## Changes between v2.0.0 and v2.1.0
8+
9+
!!! warning
10+
You must upgrade to v2.0.0 **before** installing v2.1.0. If you attempt to upgrade an existing
11+
installation running a version older than v2.0.0, the installer will report an error and
12+
exit without making any changes.
13+
14+
If you are currently on a version older than v2.0.0 and don't have access to the v2.0.0 installer
15+
anymore, please reach out to our support team for new download links.
16+
17+
### Features
18+
19+
- The stack and module settings have been revamped, making it simpler and more efficient to manage your stacks and modules. One of the standout additions is the new Scheduling and Policies tabs, which have moved from the stack settings to the main stack view. Your schedules and policies are now more easily discoverable, and can also be viewed by team members who don’t have access to stack settings.
20+
21+
### Fixes
22+
23+
- We've fixed an issue with our initial Disaster Recovery support that meant that IoT policies would not be added to your secondary region when resetting an existing worker pool that was created before DR was configured. The impact of this would have been that workers from the affected pools would not be able to connect to your IoT broker after failing over. No user intervention is required to resolve this - the v2.1.0 installation process will fix any affected worker pools.
24+
- We've fixed an issue affecting Bitbucket Data Center that prevented branches being retrieved correctly if the repository contained more than 25 branches that contained your stack's branch name as part of their name (for example if a stack has a tracked branch called `dev`, and other branches exist in the repository like `development`, `dev-1`, `dev-2`, etc). This could prevent the stack settings for an affected stack from being saved.
25+
726
## Changes between v1.3.0 and v2.0.0
827

928
!!! warning

docs/vendors/terraform/terraform-provider.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ The following table shows the latest version of the Terraform provider known to
2525

2626
| Self-Hosted Version | Max Provider Version |
2727
| ------------------- | -------------------- |
28+
| 2.1.0 | 1.15.0 |
2829
| 2.0.0 | 1.14.0 |
2930
| 1.3.0 | 1.14.0 |
3031
| 1.2.1 | 1.13.1 |

0 commit comments

Comments
 (0)