starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-25 17:05:50 +03:00

actionlint from 1.6.20 to 1.6.21 #1916

New issue

Closed

opened 2026-03-01 21:53:13 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 21:53:13 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/1380
Author: @dependabot[bot]
Created: 10/10/2022
Status: ✅ Merged
Merged: 10/10/2022
Merged by: @mergify[bot]

Base: master ← Head: dependabot/go_modules/github.com/rhysd/actionlint-1.6.21

📝 Commits (2)

fb928d2 build(deps): bump github.com/rhysd/actionlint from 1.6.20 to 1.6.21
cbe8ffe Merge branch 'master' into dependabot/go_modules/github.com/rhysd/actionlint-1.6.21

📊 Changes

2 files changed (+3 additions, -3 deletions)

View changed files

📝 go.mod (+1 -1)
📝 go.sum (+2 -2)

📄 Description

Bumps github.com/rhysd/actionlint from 1.6.20 to 1.6.21.

Release notes

Sourced from github.com/rhysd/actionlint's releases.

v1.6.21
Check contexts availability. Some contexts limit where they can be used. For example, jobs.<job_id>.env workflow key does not allow accessing env context, but jobs.<job_id>.steps.env allows. See the official document for the complete list of contexts availability. (#180)
...
env:
TOPLEVEL: ...
jobs:
test:
runs-on: ubuntu-latest
env:
# ERROR: 'env' context is not available here
JOB_LEVEL: ${{ env.TOPLEVEL }}
steps:
- env:
# OK: 'env' context is available here
STEP_LEVEL: ${{ env.TOPLEVEL }}
...
actionlint reports the context is not available and what contexts are available as follows:
test.yaml:11:22: context "env" is not allowed here. available contexts are "github", "inputs", "matrix", "needs", "secrets", "strategy". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression]
   |
11 |       JOB_LEVEL: ${{ env.TOPLEVEL }}
   |                      ^~~~~~~~~~~~
Check special functions availability. Some functions limit where they can be used. For example, status functions like success() or failure() are only available in conditions of if:. See the official document for the complete list of special functions availability. (#214)
...
steps:
ERROR: 'success()' function is not available here

run: echo 'Success? ${{ success() }}'
OK: 'success()' function is available here
if: success()
actionlint reports success() is not available and where the function is available as follows:
test.yaml:8:33: calling function "success" is not allowed here. "success" is only available in "jobs.<job_id>.if", "jobs.<job_id>.steps.if". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression]
  |
8 |       - run: echo 'Success? ${{ success() }}'
  |                                 ^~~~~~~~~
Fix inputs context is not available in run-name: section. (#223)

Allow dynamic shell configuration like shell: ${{ env.SHELL }}.

Fix no error is reported when on: does not exist at toplevel. (#232)

Fix an error position is not correct when the error happens at root node of workflow AST.

Fix an incorrect empty event is parsed when on: section is empty.

Fix the error message when parsing an unexpected key on toplevel. (#231, thanks @norwd)

... (truncated)

Changelog

Sourced from github.com/rhysd/actionlint's changelog.

v1.6.21 - 09 Oct 2022
Check contexts availability. Some contexts limit where they can be used. For example, jobs.<job_id>.env workflow key does not allow accessing env context, but jobs.<job_id>.steps.env allows. See the official document for the complete list of contexts availability. (#180)
...
env:
TOPLEVEL: ...
jobs:
test:
runs-on: ubuntu-latest
env:
# ERROR: 'env' context is not available here
JOB_LEVEL: ${{ env.TOPLEVEL }}
steps:
- env:
# OK: 'env' context is available here
STEP_LEVEL: ${{ env.TOPLEVEL }}
...
actionlint reports the context is not available and what contexts are available as follows:
test.yaml:11:22: context "env" is not allowed here. available contexts are "github", "inputs", "matrix", "needs", "secrets", "strategy". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression]
   |
11 |       JOB_LEVEL: ${{ env.TOPLEVEL }}
   |                      ^~~~~~~~~~~~
Check special functions availability. Some functions limit where they can be used. For example, status functions like success() or failure() are only available in conditions of if:. See the official document for the complete list of special functions availability. (#214)
...
steps:
ERROR: 'success()' function is not available here

run: echo 'Success? ${{ success() }}'
OK: 'success()' function is available here
if: success()
actionlint reports success() is not available and where the function is available as follows:
test.yaml:8:33: calling function "success" is not allowed here. "success" is only available in "jobs.<job_id>.if", "jobs.<job_id>.steps.if". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression]
  |
8 |       - run: echo 'Success? ${{ success() }}'
  |                                 ^~~~~~~~~
Fix inputs context is not available in run-name: section. (#223)

Allow dynamic shell configuration like shell: ${{ env.SHELL }}.

Fix no error is reported when on: does not exist at toplevel. (#232)

Fix an error position is not correct when the error happens at root node of workflow AST.

Fix an incorrect empty event is parsed when on: section is empty.

... (truncated)

Commits

bb1cfc3 bump up version to v1.6.21
79e852a update playground dependencies
28d27a9 improve example and description of contexts and special function availability...
29fe73a add test to check context availability of run-name
ce0f432 fix build broken by the previous merge
011c6a1 Merge branch 'ctx-spfn-availability' (fixes #180, fixes #214)
acac1d1 add example test for contexts and special functions availablity checks
852639b describe contexts and special function availability checks in document
9fe29a4 Merge pull request #233 from rhysd/ci/3208740685
11b4bc3 update generated files by go generate on CI
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/nektos/act/pull/1380 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 10/10/2022 **Status:** ✅ Merged **Merged:** 10/10/2022 **Merged by:** [@mergify[bot]](https://github.com/apps/mergify) **Base:** `master` ← **Head:** `dependabot/go_modules/github.com/rhysd/actionlint-1.6.21` --- ### 📝 Commits (2) - [`fb928d2`](https://github.com/nektos/act/commit/fb928d2e4846f0e48d2eafdb542bc72109d2cdae) build(deps): bump github.com/rhysd/actionlint from 1.6.20 to 1.6.21 - [`cbe8ffe`](https://github.com/nektos/act/commit/cbe8ffed23b88be9e244e5b7e9d3f41552496e90) Merge branch 'master' into dependabot/go_modules/github.com/rhysd/actionlint-1.6.21 ### 📊 Changes **2 files changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `go.mod` (+1 -1) 📝 `go.sum` (+2 -2) </details> ### 📄 Description Bumps [github.com/rhysd/actionlint](https://github.com/rhysd/actionlint) from 1.6.20 to 1.6.21. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rhysd/actionlint/releases">github.com/rhysd/actionlint's releases</a>.</em></p> <blockquote> <h2>v1.6.21</h2> <ul> <li>Check contexts availability. Some contexts limit where they can be used. For example, <code>jobs.<job_id>.env</code> workflow key does not allow accessing <code>env</code> context, but <code>jobs.<job_id>.steps.env</code> allows. See <a href="https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability">the official document</a> for the complete list of contexts availability. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/180">#180</a>) <pre lang="yaml"><code>... <p>env: TOPLEVEL: ...</p> <p>jobs: test: runs-on: ubuntu-latest env: # ERROR: 'env' context is not available here JOB_LEVEL: ${{ env.TOPLEVEL }} steps: - env: # OK: 'env' context is available here STEP_LEVEL: ${{ env.TOPLEVEL }} ... </code></pre> actionlint reports the context is not available and what contexts are available as follows:</p> <pre><code>test.yaml:11:22: context "env" is not allowed here. available contexts are "github", "inputs", "matrix", "needs", "secrets", "strategy". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression] | 11 | JOB_LEVEL: ${{ env.TOPLEVEL }} | ^~~~~~~~~~~~ </code></pre> </li> <li>Check special functions availability. Some functions limit where they can be used. For example, status functions like <code>success()</code> or <code>failure()</code> are only available in conditions of <code>if:</code>. See <a href="https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability">the official document</a> for the complete list of special functions availability. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/214">#214</a>) <pre lang="yaml"><code>... <p>steps:</p> <h1>ERROR: 'success()' function is not available here</h1> <ul> <li>run: echo 'Success? ${{ success() }}' <h1>OK: 'success()' function is available here</h1> if: success() </code></pre> actionlint reports <code>success()</code> is not available and where the function is available as follows:</li> </ul> <pre><code>test.yaml:8:33: calling function "success" is not allowed here. "success" is only available in "jobs.<job_id>.if", "jobs.<job_id>.steps.if". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression] | 8 | - run: echo 'Success? ${{ success() }}' | ^~~~~~~~~ </code></pre> </li> <li>Fix <code>inputs</code> context is not available in <code>run-name:</code> section. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/223">#223</a>)</li> <li>Allow dynamic shell configuration like <code>shell: ${{ env.SHELL }}</code>.</li> <li>Fix no error is reported when <code>on:</code> does not exist at toplevel. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/232">#232</a>)</li> <li>Fix an error position is not correct when the error happens at root node of workflow AST.</li> <li>Fix an incorrect empty event is parsed when <code>on:</code> section is empty.</li> <li>Fix the error message when parsing an unexpected key on toplevel. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/231">#231</a>, thanks <a href="https://github.com/norwd"><code>@norwd</code></a>)</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rhysd/actionlint/blob/main/CHANGELOG.md">github.com/rhysd/actionlint's changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/rhysd/actionlint/releases/tag/v1.6.21">v1.6.21</a> - 09 Oct 2022</h1> <ul> <li>Check contexts availability. Some contexts limit where they can be used. For example, <code>jobs.<job_id>.env</code> workflow key does not allow accessing <code>env</code> context, but <code>jobs.<job_id>.steps.env</code> allows. See <a href="https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability">the official document</a> for the complete list of contexts availability. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/180">#180</a>) <pre lang="yaml"><code>... <p>env: TOPLEVEL: ...</p> <p>jobs: test: runs-on: ubuntu-latest env: # ERROR: 'env' context is not available here JOB_LEVEL: ${{ env.TOPLEVEL }} steps: - env: # OK: 'env' context is available here STEP_LEVEL: ${{ env.TOPLEVEL }} ... </code></pre> actionlint reports the context is not available and what contexts are available as follows:</p> <pre><code>test.yaml:11:22: context "env" is not allowed here. available contexts are "github", "inputs", "matrix", "needs", "secrets", "strategy". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression] | 11 | JOB_LEVEL: ${{ env.TOPLEVEL }} | ^~~~~~~~~~~~ </code></pre> </li> <li>Check special functions availability. Some functions limit where they can be used. For example, status functions like <code>success()</code> or <code>failure()</code> are only available in conditions of <code>if:</code>. See <a href="https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability">the official document</a> for the complete list of special functions availability. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/214">#214</a>) <pre lang="yaml"><code>... <p>steps:</p> <h1>ERROR: 'success()' function is not available here</h1> <ul> <li>run: echo 'Success? ${{ success() }}' <h1>OK: 'success()' function is available here</h1> if: success() </code></pre> actionlint reports <code>success()</code> is not available and where the function is available as follows:</li> </ul> <pre><code>test.yaml:8:33: calling function "success" is not allowed here. "success" is only available in "jobs.<job_id>.if", "jobs.<job_id>.steps.if". see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability for more details [expression] | 8 | - run: echo 'Success? ${{ success() }}' | ^~~~~~~~~ </code></pre> </li> <li>Fix <code>inputs</code> context is not available in <code>run-name:</code> section. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/223">#223</a>)</li> <li>Allow dynamic shell configuration like <code>shell: ${{ env.SHELL }}</code>.</li> <li>Fix no error is reported when <code>on:</code> does not exist at toplevel. (<a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/232">#232</a>)</li> <li>Fix an error position is not correct when the error happens at root node of workflow AST.</li> <li>Fix an incorrect empty event is parsed when <code>on:</code> section is empty.</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rhysd/actionlint/commit/bb1cfc39e910ad6feced2b4fd77bc26fdad9aa71"><code>bb1cfc3</code></a> bump up version to v1.6.21</li> <li><a href="https://github.com/rhysd/actionlint/commit/79e852a62e44a3d99c1e44613adb0fb19391eaf5"><code>79e852a</code></a> update playground dependencies</li> <li><a href="https://github.com/rhysd/actionlint/commit/28d27a93280079beb55f75524d53e56251ed8d44"><code>28d27a9</code></a> improve example and description of contexts and special function availability...</li> <li><a href="https://github.com/rhysd/actionlint/commit/29fe73a1dc82e290127696dce6c06161157f1389"><code>29fe73a</code></a> add test to check context availability of <code>run-name</code></li> <li><a href="https://github.com/rhysd/actionlint/commit/ce0f432077f734cf4776e7368975b5a6adea6846"><code>ce0f432</code></a> fix build broken by the previous merge</li> <li><a href="https://github.com/rhysd/actionlint/commit/011c6a1a2a18b675dc3476751243a6462175d31d"><code>011c6a1</code></a> Merge branch 'ctx-spfn-availability' (fixes <a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/180">#180</a>, fixes <a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/214">#214</a>)</li> <li><a href="https://github.com/rhysd/actionlint/commit/acac1d1daaf8fa9ce01f03c9fb6a0313f25dca13"><code>acac1d1</code></a> add example test for contexts and special functions availablity checks</li> <li><a href="https://github.com/rhysd/actionlint/commit/852639b73cb81fe04a742f54245eef7f55642a10"><code>852639b</code></a> describe contexts and special function availability checks in document</li> <li><a href="https://github.com/rhysd/actionlint/commit/9fe29a449c194d0ff12a3b08c998c524ef290013"><code>9fe29a4</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/rhysd/actionlint/issues/233">#233</a> from rhysd/ci/3208740685</li> <li><a href="https://github.com/rhysd/actionlint/commit/11b4bc31815ab86761e7b4443687c3cd7c07f047"><code>11b4bc3</code></a> update generated files by <code>go generate</code> on CI</li> <li>Additional commits viewable in <a href="https://github.com/rhysd/actionlint/compare/v1.6.20...v1.6.21">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/rhysd/actionlint&package-manager=go_modules&previous-version=1.6.20&new-version=1.6.21)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-01 21:53:13 +03:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1916

No description provided.

Rows
Columns