Releases: cloudposse/github-action-atmos-terraform-drift-detection
v2.0.0
Major Version Update for Artifacts @milldr (#1682)
# Breaking Changes!Context
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
ℹ️ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads must use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.
https://github.com/actions/upload-artifact/releases/tag/v4.0.0
TLDR
- The version of
@actions/artifact
used to upload and download an artifact must match. - We upload the Terraform plan file artifact with cloudposse/github-action-atmos-terraform-plan
- We want to upgrade the version of
upload-artifact
in that action, so we must also upgrade in this action
What do I need to do?
Bump both actions to these versions once both major upgrades are released:
cloudposse/github-action-atmos-terraform-drift-detection@v2
cloudposse/github-action-atmos-terraform-plan@3
PR Notes
what
- Corrected structure for
downloadArtifact
for usage withv2
of@actions/artifact
- Replaced all actions used in tests with deprecated versions of Node
- Rebuild node modules
why
- Resolve the breaking changes made with
v2
: https://github.com/actions/toolkit/blob/main/packages/artifact/README.md#breaking-changes - Resolve warning messages on GitHub Action workflows
- Use the latest modules for the existing
package.json
references
v1.2.1
fix(deps): update dependency @actions/artifact to v1.1.2 @renovate (#1209)
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
@actions/artifact (source) | 1.1.1 -> 1.1.2 |
chore(deps): update dependency jest to v29.7.0 @renovate (#1250)
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
jest (source) | 29.6.4 -> 29.7.0 |
Release Notes
jestjs/jest (jest)
v29.7.0
Features
[create-jest]
Addnpm init
/yarn create
initialiser for Jest projects (#14465)[jest-validate]
Allow deprecation warnings for unknown options (#14499)
Fixes
[jest-resolver]
Replace unmatched capture groups inmoduleNameMapper
with empty string instead ofundefined
(#14507)[jest-snapshot]
Allow for strings as well as template literals in inline snapshots (#14465)[@jest/test-sequencer]
Calculate test runtime ifperStats.duration
is missing (#14473)
Performance
[@jest/create-cache-key-function]
Cache access ofNODE_ENV
andBABEL_ENV
(#14455)
Chore & Maintenance
[jest-cli]
Move internal config initialisation logic to thecreate-jest
package (#14465)
chore(deps): update dependency eslint-plugin-jest to v27.9.0 @renovate (#1249)
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
eslint-plugin-jest | 27.2.3 -> 27.9.0 |
Release Notes
jest-community/eslint-plugin-jest (eslint-plugin-jest)
v27.9.0
Features
v27.8.0
Features
v27.7.0
Features
27.6.3 (2024-01-12)
Bug Fixes
27.6.2 (2024-01-10)
Reverts
27.6.1 (2024-01-01)
Bug Fixes
v27.6.3
Bug Fixes
v27.6.2
Reverts
v27.6.1
Bug Fixes
v27.6.0
Features
v27.5.0
[Compare Source](https://togithub.com/jest-community/eslint-plugin-jest/compare/v27...
v1.2.0
v1.1.0
v1.0.0
Added post comment to PR @goruha (#466)
Feature request
- Comment on PR when merged without auto-apply
[!IMPORTANT]
No Changes Were AppliedThis Pull Request was merged without using the
auto-apply
label.
Please check if any issues were created and apply them by adding theapply
label to the corresponding issue.
what
- Added comment to PR
why
- Improve informative feedback for developers
references
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#6)
what
This is an auto-generated PR that updates the README.md and docs
why
To have most recent changes of README.md and doc from origin templates
v0.7.0
Refactor GHA @goruha (#189)
what
- Refactoring of the action
- Added tests
- Added
process-all
flag - Fix the action failure in case all affected stacks have not changed (artifact does not exist)
- Fix the bug when an issue has wrong metadata or no metadata at all
- Fix the bug when the summary size runs out of 1Mb limit
why
- Improve code readability
- Gain insurance in the action stability
- Fix the bug when the action runs in the
apply
workflow to close issues created by thedrift detection
workflow. - Fix apply and drift detection workflow when there is no stack with drift or error
- Avoid failing of
apply
anddrift detection
workflows because of wrong metadata in one issue - Avoid errors because a summary is too big
references
- https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#step-isolation-and-limits
- https://cloudposse.atlassian.net/browse/DEV-1562
- https://cloudposse.atlassian.net/browse/DEV-1561
- https://cloudposse.atlassian.net/browse/DEV-1560
- https://cloudposse.atlassian.net/browse/DEV-1555
- https://cloudposse.atlassian.net/browse/DEV-1559
- https://cloudposse.atlassian.net/browse/DEV-1135
v0.6.0
fix: summary file crashes @dudymas (#305)
what
- fix(action): look for descriptions before loading them
- fix(action/file_name): replace all instances of slash
why
- If a component has multiple slashes in its name, it won't be found
- if a file isn't found, the reconcile workflow exits immediately instead of
skipping