Sourced from actions/checkout's releases.
v7.0.1
What's Changed
- skip running unsafe pr check if input is default by
@aiqiaoyin actions/checkout#2518- trim only ascii whitespace for branch by
@aiqiaoyin actions/checkout#2521- escape values passed to --unset by
@aiqiaoyin actions/checkout#2530- Various dependency updates
Full Changelog: https://github.com/actions/checkout/compare/v7...v7.0.1
Sourced from actions/checkout's changelog.
Changelog
v7.0.1
- Skip running unsafe pr check if input is default by
@aiqiaoyin actions/checkout#2518- Trim only ascii whitespace for branch by
@aiqiaoyin actions/checkout#2521- Escape values passed to --unset by
@aiqiaoyin actions/checkout#2530- Various dependency updates
v7.0.0
- Block checking out fork PR for pull_request_target and workflow_run by
@aiqiaoyin actions/checkout#2454- Various dependency updates
v6.0.3
- Fix checkout init for SHA-256 repositories by
@yaananthin actions/checkout#2439- fix: expand merge commit SHA regex and add SHA-256 test cases by
@yaananthin actions/checkout#2414v6.0.2
- Fix tag handling: preserve annotations and explicit fetch-tags by
@ericsciplein actions/checkout#2356v6.0.1
- Add worktree support for persist-credentials includeIf by
@ericsciplein actions/checkout#2327v6.0.0
- Persist creds to a separate file by
@ericsciplein actions/checkout#2286- Update README to include Node.js 24 support details and requirements by
@salmanmkcin actions/checkout#2248v5.0.1
- Port v6 cleanup to v5 by
@ericsciplein actions/checkout#2301v5.0.0
- Update actions checkout to use node 24 by
@salmanmkcin actions/checkout#2226v4.3.1
- Port v6 cleanup to v4 by
@ericsciplein actions/checkout#2305v4.3.0
- docs: update README.md by
@motssin actions/checkout#1971- Add internal repos for checking out multiple repositories by
@mouismailin actions/checkout#1977- Documentation update - add recommended permissions to Readme by
@benwellsin actions/checkout#2043- Adjust positioning of user email note and permissions heading by
@joshmgrossin actions/checkout#2044- Update README.md by
@nebuk89in actions/checkout#2194- Update CODEOWNERS for actions by
@TingluoHuangin actions/checkout#2224- Update package dependencies by
@salmanmkcin actions/checkout#2236v4.2.2
url-helper.tsnow leverages well-known environment variables by@jww3in actions/checkout#1941- Expand unit test coverage for
isGhesby@jww3in actions/checkout#1946v4.2.1
- Check out other refs/* by commit if provided, fall back to ref by
@orhantoyin actions/checkout#1924
... (truncated)
3d3c42e
prep v7.0.1 release (#2531)2880268
escape values passed to --unset (#2530)12cd223
trim only ascii whitespace for branch (#2521)62661c4
skip running unsafe pr check if input is default (#2518)e8d4307
Bump the minor-actions-dependencies group with 2 updates (#2499)631c942
eslint 9 (#2474)4f1f4ae
Bump actions/upload-artifact from 4 to 7 (#2476)ba09753
Bump actions/checkout from 6 to 7 (#2488)b9e0990
Bump docker/login-action from 3.3.0 to 4.2.0 (#2479)e8cb398
Bump docker/build-push-action from 6.5.0 to 7.2.0 (#2478)Sourced from actions/setup-go's releases.
v7.0.0
What's Changed
- Migrate to ESM and upgrade dependencies by
@priyagupta108in actions/setup-go#763- chore(deps): bump
@actions/cacheto 6.2.0 by@philip-gaiin actions/setup-go#771New Contributors
@philip-gaimade their first contribution in actions/setup-go#771Full Changelog: https://github.com/actions/setup-go/compare/v6...v7.0.0
b7ad1da
chore(deps): bump @actions/cache to 6.2.0 (#771)0778a10
Migrate to ESM and upgrade dependencies (#763)Sourced from actions/setup-java's releases.
v5.6.0
What's Changed
- Backport to v5: Add Maven compiler problem matcher for javac diagnostics by
@brunoborgesin actions/setup-java#1087- feat: expose cache-primary-key output (#597) [v5 backport] by
@brunoborgesin actions/setup-java#1089- dist: Cover Tencent Kona JDK 25 (#1108) [v5 backport] by
@brunoborgesin actions/setup-java#1110- Backport #1111: Preserve Maven toolchains across repeated setup-java runs (#1099) by
@brunoborgesin actions/setup-java#1113- Backport #1097/#1098 to v5: cache Maven and Gradle wrapper distributions separately by
@brunoborgesin actions/setup-java#1122Full Changelog: https://github.com/actions/setup-java/compare/v5...v5.6.0
v5.5.0
What's Changed
- chore: enforce pre-PR validation (aggregate scripts, git hooks, PR checklist) by
@brunoborgesin actions/setup-java#1061- Bump github/codeql-action from 3 to 4 by
@dependabot[bot] in actions/setup-java#1069- Bump actions/checkout from 6 to 7 by
@dependabot[bot] in actions/setup-java#1068- Bump actions/setup-python from 5 to 6 by
@dependabot[bot] in actions/setup-java#1067- Bump
@typescript-eslint/parserfrom 8.61.1 to 8.62.0 by@dependabot[bot] in actions/setup-java#1062- feat: Add verify-signature plumbing and Temurin+Microsoft verification support by
@johnoliverin actions/setup-java#1060- Updated jetbrains test: https.request() now catches errors. This fixes leaking tests as well by
@jmjaffe37in actions/setup-java#1070- Fix arm64 e2e workflow tests mislabeled as x64 by
@brunoborgeswith@Copilotin actions/setup-java#1073- feat: suppress Maven transfer progress via MAVEN_ARGS by default (add show-download-progress input) by
@brunoborgesin actions/setup-java#1053- feat: Disable interactiveMode in generated Maven settings.xml by
@brunoborgeswith@Copilotin actions/setup-java#1052- Bump prettier from 3.6.2 to 3.9.1 by
@dependabot[bot] in actions/setup-java#1066- chore(deps-dev): bump eslint-plugin-jest from 29.0.1 to 29.15.4 by
@dependabot[bot] in actions/setup-java#1074- fix: Maven Toolchains grows unexpectedly by
@Okeanosin actions/setup-java#534- dist: Support Tencent Kona JDK by
@johnshajiangin actions/setup-java#672- feat: Add set-default option by
@gsmetin actions/setup-java#1017- docs: document problem matcher (and how to disable it), Maven Wrapper caching, and generated interactiveMode by
@brunoborgesin actions/setup-java#1075- feat: Add distribution detection support to .sdkmanrc file by
@lukaszgygin actions/setup-java#975New Contributors
@jmjaffe37made their first contribution in actions/setup-java#1070@gsmetmade their first contribution in actions/setup-java#1017@lukaszgygmade their first contribution in actions/setup-java#975Full Changelog: https://github.com/actions/setup-java/compare/v5...v5.5.0
03ad4de
Backport #1097/#1098:
cache Maven and Gradle wrapper distributions separately...d229d2e
Backport #1111:
Preserve Maven toolchains across repeated setup-java runs (#1...bbf0f69
dist: Cover Tencent Kona JDK 25 (#1110)513edc4
feat: expose cache-primary-key output (#597)
[v5 backport] (#1089)62df799
Add Maven compiler problem matcher for javac diagnostics (#1087)176156a
chore: bump version to 5.6.0 for v5 release linebf7b8de
build: rebuild dist for backported changes (#1079,
#1083,
#1084)0173e6d
Infer distribution from asdf .tool-versions vendor prefix (#1084)f45cd82
Rename jdkFile input to jdk-file with deprecated alias (#1083)e2863ad
Map Zulu x86 architecture to i686 for Azul Metadata API (#1079)Sourced from jdx/mise-action's releases.
v4.2.3: Restore mise PATH propagation
A patch release that restores mise's PATH propagation to subsequent workflow steps — without reintroducing the full-PATH snapshot behavior that v4.2.1 fixed.
Fixed
Export mise PATH entries to subsequent steps (#575) by
@jdxv4.2.1 stopped exporting the complete
PATHreturned bymise env --jsonintoGITHUB_ENV, which correctly prevented snapshotting the runner's environment into subsequent steps. However, that also dropped mise-produced PATH entries — tool shims,[env] _.pathdirectories, and similar — that workflows relied on after the setup step. See #565.The action now computes only the prefix that mise prepended to the existing
PATHand forwards those directories individually throughGITHUB_PATH. This preserves mise's configured ordering, composes cleanly with PATH changes from other actions, and never persists the runner's fullPATHthroughGITHUB_ENV. The dotenv fallback path (used with older mise versions) also stripsPATH=lines and re-derives additions frommise env --json.A new
export_pathinput (defaulttrue) lets workflows keep regularenvexports while opting out of PATH changes:- uses: jdx/mise-action@v4 with: export_path: false # keep env vars, skip mise PATH additionsFull Changelog: https://github.com/jdx/mise-action/compare/v4.2.2...v4.2.3
v4.2.2: Zstd tar fallback for older runners
A small patch release that fixes archive selection on runners with an older
tarand corrects a stale default in the README.Fixed
Verify
tarsupports Zstd before picking.tar.zst(#569 by@JackMyers001The action previously chose the
.tar.zstmise archive wheneverzstd --versionsucceeded, then extracted it withtar --zstd. On RHEL 8-compatible runners that shipzstd1.4.4 alongside GNUtar1.30, the--zstdoption isn't recognized and installation failed.Detection now runs both checks:
zstd --version tar --zstd --versionIf either fails, the action falls back to the
.tar.gzarchive. No configuration change is required — existing workflows on affected runners just start working again. Fixes #568.Documentation
- Update the
cache_key_prefixexample in the README to reflect the current default ofmise-v1(previously documented asmise-v0) (#570 by@muzimuzhi).New Contributors
@JackMyers001made their first contribution in #569@muzimuzhimade their first contribution in #570Full Changelog: https://github.com/jdx/mise-action/compare/v4.2.1...v4.2.2
... (truncated)
Sourced from jdx/mise-action's changelog.
Changelog
4.2.4 - 2026-07-28
🐛 Bug Fixes
4.2.3 - 2026-07-24
🐛 Bug Fixes
4.2.2 - 2026-07-24
🐛 Bug Fixes
- (release-plz) exit when git-cliff produces no version bump (#566) by
@jdxin #566- ensure
tarsupports Zstd (#569) by@JackMyers001in #569📚 Documentation
- update default value of
cache_key_prefix(#570) by@muzimuzhiin #570New Contributors
@muzimuzhimade their first contribution in #570@JackMyers001made their first contribution in #569
4.2.1 - 2026-07-16
🐛 Bug Fixes
- verify mise downloads with signed checksums (#548) by
@jdxin #548- exclude PATH from environment export (#556) by
@jdxin #556🔍 Other Changes
⚙️ Miscellaneous Tasks
... (truncated)
9e7f763
chore: release v4.2.3 (#578)0f85637
fix: export mise path entries to subsequent steps (#575)a24c375
chore(deps): migrate to aube lockfile (#576)f10502f
chore: release v4.2.2 (#567)5df6b79
chore(deps): update zizmorcore/zizmor-action action to v0.6.0 (#574)be707ec
chore(deps): update jdx/mise-action action to v4.2.1 (#572)d0f7879
chore(deps): update github/codeql-action action to v4.37.1 (#571)fc371b7
docs: update default value of cache_key_prefix (#570)5c77551
fix: ensure tar supports Zstd (#569)a63ca4f
fix(release-plz): exit when git-cliff produces no version bump (#566)Sourced from github/codeql-action/init's releases.
v4.37.3
No user facing changes.
v4.37.2
- The new address format for the
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023- The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007
v4.37.1
- Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
- Update default CodeQL bundle version to 2.26.1. #4019
v4.37.0
- Update default CodeQL bundle version to 2.26.0. #3995
- In addition to the existing input format, the
config-fileinput for thecodeql-action/initstep will soon support a new[owner/]repo[@ref][:path]format. All components except the repository name are optional. If omitted,ownerdefaults to the same owner as the repository the analysis is running for,reftomain, andpathto.github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973v4.36.3
No user facing changes.
Sourced from github/codeql-action/init's changelog.
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
[UNRELEASED]
- Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the
initAction instead of falling back to downloading the bundle before extracting it. #40614.37.4 - 29 Jul 2026
- This version of the CodeQL Action adds support for the
toolsinput for thecodeql-action/initstep to be specified using agithub-codeql-toolsrepository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value totoolcacheto always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided fortoolsin the workflow definition always takes precedence unless the value of the repository property starts with!. #4037- Update default CodeQL bundle version to 2.26.2. #4051
4.37.3 - 22 Jul 2026
No user facing changes.
4.37.2 - 21 Jul 2026
- The new address format for the
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023- The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007
4.37.1 - 16 Jul 2026
- Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
- Update default CodeQL bundle version to 2.26.1. #4019
4.37.0 - 08 Jul 2026
- Update default CodeQL bundle version to 2.26.0. #3995
- In addition to the existing input format, the
config-fileinput for thecodeql-action/initstep will soon support a new[owner/]repo[@ref][:path]format. All components except the repository name are optional. If omitted,ownerdefaults to the same owner as the repository the analysis is running for,reftomain, andpathto.github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #39734.36.3 - 01 Jul 2026
No user facing changes.
4.36.2 - 04 Jun 2026
- Cache CodeQL CLI version information across Actions steps. #3943
- Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
- Update default CodeQL bundle version to 2.25.6. #3948
4.36.1 - 02 Jun 2026
No user facing changes.
4.36.0 - 22 May 2026
... (truncated)
e4fba86
Merge pull request #4031
from github/update-v4.37.3-72f6a9da0fb50ab5
Update changelog for v4.37.372f6a9d
Merge pull request #4030
from github/mbg/fix/no-proxy3b5ee58
Use default request options instead of
undefinedbfb6be4
Merge pull request #4028
from github/mergeback/v4.37.2-to-main-e0647621526ab84
Rebuildd6217b9
Update changelog and version after v4.37.2e064762
Merge pull request #4027
from github/update-v4.37.2-385bcdc5ae0faed8
Add a couple of change notes73aad0e
Update changelog for v4.37.2Sourced from github/codeql-action/analyze's releases.
v4.37.3
No user facing changes.
v4.37.2
- The new address format for the
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023- The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007
v4.37.1
- Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
- Update default CodeQL bundle version to 2.26.1. #4019
v4.37.0
- Update default CodeQL bundle version to 2.26.0. #3995
- In addition to the existing input format, the
config-fileinput for thecodeql-action/initstep will soon support a new[owner/]repo[@ref][:path]format. All components except the repository name are optional. If omitted,ownerdefaults to the same owner as the repository the analysis is running for,reftomain, andpathto.github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973v4.36.3
No user facing changes.
Sourced from github/codeql-action/analyze's changelog.
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
[UNRELEASED]
- Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the
initAction instead of falling back to downloading the bundle before extracting it. #40614.37.4 - 29 Jul 2026
- This version of the CodeQL Action adds support for the
toolsinput for thecodeql-action/initstep to be specified using agithub-codeql-toolsrepository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value totoolcacheto always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided fortoolsin the workflow definition always takes precedence unless the value of the repository property starts with!. #4037- Update default CodeQL bundle version to 2.26.2. #4051
4.37.3 - 22 Jul 2026
No user facing changes.
4.37.2 - 21 Jul 2026
- The new address format for the
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023- The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007
4.37.1 - 16 Jul 2026
- Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
- Update default CodeQL bundle version to 2.26.1. #4019
4.37.0 - 08 Jul 2026
- Update default CodeQL bundle version to 2.26.0. #3995
- In addition to the existing input format, the
config-fileinput for thecodeql-action/initstep will soon support a new[owner/]repo[@ref][:path]format. All components except the repository name are optional. If omitted,ownerdefaults to the same owner as the repository the analysis is running for,reftomain, andpathto.github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #39734.36.3 - 01 Jul 2026
No user facing changes.
4.36.2 - 04 Jun 2026
- Cache CodeQL CLI version information across Actions steps. #3943
- Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
- Update default CodeQL bundle version to 2.25.6. #3948
4.36.1 - 02 Jun 2026
No user facing changes.
4.36.0 - 22 May 2026
... (truncated)
e4fba86
Merge pull request #4031
from github/update-v4.37.3-72f6a9da0fb50ab5
Update changelog for v4.37.372f6a9d
Merge pull request #4030
from github/mbg/fix/no-proxy3b5ee58
Use default request options instead of
undefinedbfb6be4
Merge pull request #4028
from github/mergeback/v4.37.2-to-main-e0647621526ab84
Rebuildd6217b9
Update changelog and version after v4.37.2e064762
Merge pull request #4027
from github/update-v4.37.2-385bcdc5ae0faed8
Add a couple of change notes73aad0e
Update changelog for v4.37.2Sourced from lycheeverse/lychee-action's releases.
v2.9.0
Summary
This release updates the default lychee version from
v0.23.0tov0.24.2.The main reason for this release is compatibility with the new lychee
0.24.xrelease artifacts. Starting with lycheev0.24.0, the archive layout changed, and thelycheebinary may now be packaged inside a subdirectory.lychee-actionnow detects that layout automatically, so users can upgrade without changing their workflows.If you use:
uses: lycheeverse/lychee-action@v2you will get the new version once the floating
v2tag has been updated. If you pin exact versions, update to:uses: lycheeverse/lychee-action@v2.9.0What’s new from lychee
v0.24.xBetter diagnostics
lychee now reports line and column numbers for detected links. This makes broken link reports easier to act on, especially in larger documentation sites or generated reports.
Text fragment checking
lychee can now check URL text fragments, such as links containing
#:~:text=.... This helps catch links that point to a valid page but no longer points to the intended highlighted text.Sitemap support
lychee can now read
sitemap.xmlinputs. This is useful for checking published websites or generated documentation sites where the sitemap is the easiest source of URLs to validate.JUnit output
lychee now supports JUnit output. This makes it easier to integrate link checking results with CI systems and test reporting tools that understand JUnit XML.
Redirect and remap visibility
lychee can now show redirects and remaps more clearly. This helps explain why a URL was checked as a different final URL and makes debugging link-checking behavior easier.
Multiple config files
lychee now supports multiple configuration files and expanded config handling. This is useful for repositories that split documentation, website, or package-specific link-checking settings.
Timeout handling
lychee can now accept timeouts explicitly. This gives users more control over how strict their link checks should be for flaky or slow endpoints.
Fixes and reliability improvements
... (truncated)
e747777
Bump actions/cache from 5 to 6 (#340)39066c6
Bump actions/checkout from 6 to 7 (#339)6da1d14
Install into $RUNNER_TEMP instead of $HOME (#338)a63497c
fixes #322
check for null (#336)b40e218
[create-pull-request] automated changefaea714
bump default to 0.24.1 and auto-detect lychee bin in subfolder (#330)Sourced from slackapi/slack-github-action's releases.
Slack GitHub Action v4.0.0
Major Changes
b1974f0: build: parse yaml with more strict multiline indentation rules
Internal dependencies of
js-yaml@v5make YAML parsing more strict and compliant with the YAML specification. Indentation is now required for values that span multiple lines against the base value.See the YAML line prefixes spec for the expected indentation rule:
channel: "C0123" text: "first line
- second line"
- second line"
Patch Changes
- 654bb72: chore: provide global fetch proxied configurations with updates to web api and webhook packages
Slack GitHub Action v3.0.5
Patch Changes
- 96fddbe: fix: revert multiline yaml parsing indentation change
Slack GitHub Action v3.0.4
Patch Changes
- fa03fe4: refactor: send webhooks with the
@slack/webhookpackage
Sourced from slackapi/slack-github-action's changelog.
slack-github-action
4.0.0
Major Changes
b1974f0: build: parse yaml with more strict multiline indentation rules
Internal dependencies of
js-yaml@v5make YAML parsing more strict and compliant with the YAML specification. Indentation is now required for values that span multiple lines against the base value.See the YAML line prefixes spec for the expected indentation rule:
channel: "C0123" text: "first line
- second line"
- second line"
Patch Changes
- 654bb72: chore: provide global fetch proxied configurations with updates to web api and webhook packages
3.0.5
Patch Changes
- 96fddbe: fix: revert multiline yaml parsing indentation change
3.0.4
Patch Changes
- fa03fe4: refactor: send webhooks with the
@slack/webhookpackage3.0.3
Patch Changes
- 66834e4: feat: add instrumentation to address error rates
3.0.2
Patch Changes
- 79529d7: fix: resolve url.parse deprecation warning for webhook techniques
dcb1066
chore: release53861e0
chore: release (#645)