forgejo/runner
31
87
Fork 91
Code Issues 38 Pull requests 9 Releases 81 Packages 1 Activity Actions

Update https://data.forgejo.org/actions/setup-forgejo action to v3.1.3 #1331

Merged
mfenniak merged 1 commit from renovate/https-data.forgejo.org-actions-setup-forgejo-3.x into main 2026-01-26 03:20:21 +00:00
Conversation 6 Commits 1 Files changed 4 +4 -4
viceice-bot commented 2026-01-24 03:01:25 +00:00
Member
Copy link

This PR contains the following updates:

Package Type Update Change
https://data.forgejo.org/actions/setup-forgejo action patch v3.1.1 → v3.1.3

Release Notes

actions/setup-forgejo (https://data.forgejo.org/actions/setup-forgejo)

v3.1.3

Compare Source

  • other
    • PR: Update dependency forgejo/runner to v12.6.2

v3.1.2

Compare Source

  • other
    • PR: Update dependency forgejo/runner to v12.6.1
    • PR: Update dependency forgejo/runner to v12.6.0

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [https://data.forgejo.org/actions/setup-forgejo](https://code.forgejo.org/actions/setup-forgejo) | action | patch | `v3.1.1` → `v3.1.3` | --- ### Release Notes <details> <summary>actions/setup-forgejo (https://data.forgejo.org/actions/setup-forgejo)</summary> ### [`v3.1.3`](https://code.forgejo.org/actions/setup-forgejo/releases/tag/v3.1.3) [Compare Source](https://code.forgejo.org/actions/setup-forgejo/compare/v3.1.2...v3.1.3) <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/actions/setup-forgejo--> - other - [PR](https://code.forgejo.org/actions/setup-forgejo/pulls/860): <!--number 860 --><!--line 0 --><!--description VXBkYXRlIGRlcGVuZGVuY3kgZm9yZ2Vqby9ydW5uZXIgdG8gdjEyLjYuMg==-->Update dependency forgejo/runner to v12.6.2<!--description--> <!--end release-notes-assistant--> ### [`v3.1.2`](https://code.forgejo.org/actions/setup-forgejo/releases/tag/v3.1.2) [Compare Source](https://code.forgejo.org/actions/setup-forgejo/compare/v3.1.1...v3.1.2) <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/actions/setup-forgejo--> - other - [PR](https://code.forgejo.org/actions/setup-forgejo/pulls/852): <!--number 852 --><!--line 0 --><!--description VXBkYXRlIGRlcGVuZGVuY3kgZm9yZ2Vqby9ydW5uZXIgdG8gdjEyLjYuMQ==-->Update dependency forgejo/runner to v12.6.1<!--description--> - [PR](https://code.forgejo.org/actions/setup-forgejo/pulls/846): <!--number 846 --><!--line 0 --><!--description VXBkYXRlIGRlcGVuZGVuY3kgZm9yZ2Vqby9ydW5uZXIgdG8gdjEyLjYuMA==-->Update dependency forgejo/runner to v12.6.0<!--description--> <!--end release-notes-assistant--> </details> --- ### Configuration 📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi44NS4zIiwidXBkYXRlZEluVmVyIjoiNDIuOTIuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiS2luZC9EZXBlbmRlbmN5VXBkYXRlIiwicnVuLWVuZC10by1lbmQtdGVzdHMiXX0=-->
cascading-pr commented 2026-01-24 03:10:41 +00:00
Contributor
Copy link

cascading-pr updated at actions/setup-forgejo#857

cascading-pr updated at https://code.forgejo.org/actions/setup-forgejo/pulls/857
viceice commented 2026-01-24 08:07:38 +00:00
Owner
Copy link

test failure

https://code.forgejo.org/forgejo/runner/actions/runs/15801/jobs/0/attempt/1#jobstep-3-3563

[Build release/release] ⭐ Run Main https://data.forgejo.org/docker/setup-buildx-action@v3
[Build release/release]   | (node:983) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
[Build release/release]   | (Use `node --trace-deprecation ...` to show where the warning was created)
[Build release/release]   ❗  ::error::Input does not meet YAML 1.2 "Core Schema" specification: keep-state%0ASupport boolean input list: `true | True | TRUE | false | False | FALSE`

🤔

test failure https://code.forgejo.org/forgejo/runner/actions/runs/15801/jobs/0/attempt/1#jobstep-3-3563 ``` [Build release/release] ⭐ Run Main https://data.forgejo.org/docker/setup-buildx-action@v3 [Build release/release] | (node:983) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. [Build release/release] | (Use `node --trace-deprecation ...` to show where the warning was created) [Build release/release] ❗ ::error::Input does not meet YAML 1.2 "Core Schema" specification: keep-state%0ASupport boolean input list: `true | True | TRUE | false | False | FALSE` ``` 🤔
mfenniak commented 2026-01-25 04:11:47 +00:00
Owner
Copy link

I haven't been able to track this down, but here's some artifacts from investigation so far.

This error originates from:

Lines 371 to 372 in 6bc9539
throw new TypeError(`Input does not meet YAML 1.2 "Core Schema" specification: ${name}\n` +
`Support boolean input list: \`true | True | TRUE | false | False | FALSE\``);

This is part of the ${{ hashfiles(...) }} routine.

So... it seems like something is calling hashfiles on the action, which I can't find. The actual contents in setup-buildx-action look like they should be valid, as well.

I'll try to perform similar simulations of build-release.yml in the near future and see if I can reproduce this problem on a local Forgejo/Runner, which would allow sprinkling it with some logging to see what is happening. At the moment it's a bit obscure, but at least I can see relevant changes being around, just not connecting up.

I don't know if it actually says there's a problem in Runner v12.6.1. It's possible it's only a problem in the repo's workflows due to some of these action bumps. I'm not sure though.

I haven't been able to track this down, but here's some artifacts from investigation so far. This error originates from: https://code.forgejo.org/forgejo/runner/src/commit/6bc95392821624ad79f7bdc7f682bafe372202a0/act/runner/hashfiles/index.js#L371-L372 This is part of the `${{ hashfiles(...) }}` routine. - This PR bumps setup-forgejo, which upgrade includes runner v12.5.3 -> v12.6.1. build-release-integration.yml is testing build-release.yml executing on the updated Forgejo and updated Runner, but testing `build-release.yml` from this branch (unmodified, though). - Runner diff: https://code.forgejo.org/forgejo/runner/compare/v12.5.3...v12.6.1 - This update included the build-release.yml action updating forgejo/forgejo-build-publish from v5.4.1 -> v5.5.1 - forgejo-build-publish diff: https://code.forgejo.org/forgejo/forgejo-build-publish/compare/v5.4.1...v5.5.1#diff-7ab86e7f747580fef0b03d30b0ed0d9d882cf836 - This update included pushing docker/build-push-action from v2 -> v3 - This update included https://code.forgejo.org/docker/setup-buildx-action/commit/36590ad0c188499a27159a23cb004d12bdcf695e#diff-311d8554708cd4816e36e38b191057ccdbc21722 - This commit added the `keep-state` input, which is noted in the error message. So... it seems like something is calling `hashfiles` on the action, which I can't find. The actual contents in setup-buildx-action look like they should be valid, as well. I'll try to perform similar simulations of `build-release.yml` in the near future and see if I can reproduce this problem on a local Forgejo/Runner, which would allow sprinkling it with some logging to see what is happening. At the moment it's a bit obscure, but at least I can see relevant changes being around, just not connecting up. I don't know if it actually says there's a problem in Runner v12.6.1. It's possible it's only a problem in the repo's workflows due to some of these action bumps. I'm not sure though.
mfenniak commented 2026-01-25 18:20:01 +00:00
Owner
Copy link

I've identified the problem. The keep-state input it sent to the node process of setup-buildx by an environment variable, INPUT_KEEP-STATE.

As part of replacing lxc-enter with nsenter, I used a small shell script with /bin/sh to change the current process's cgroup to .lxc, matching the lxc-enter behaviour:

Lines 306 to 309 in 6bc9539
"/bin/sh",
"-c",
`echo $$ > /sys/fs/cgroup/.lxc/cgroup.procs 2>/dev/null || true; exec $@`,
"/bin/sh",

Experimentally, it seems that /bin/sh is stripping out the INPUT_KEEP-STATE environment variable. This may be considered consistent with its documentation; /bin/sh in Debian is implemented by dash, does this: "When starting up, the shell turns all the environment variables into shell variables.", and the POSIX standard for environment variables are that they consist solely of uppercase letters, digits, and underscores, resulting in /bin/sh stripping out INPUT_KEEP-STATE because it has a dash in it.

That causes setup-buildx to fail because it's looking for INPUT_KEEP-STATE to have a value and it's a required field. I have a fix in hand to replace /bin/sh with /bin/bash which addresses the bug, and I'm testing it.

At the moment, runner v12.6.0 & v12.6.1 are impacted and will fail to pass environment variables and inputs to actions which include a - in the name, when using the LXC environment.

I've identified the problem. The `keep-state` input it sent to the node process of `setup-buildx` by an environment variable, `INPUT_KEEP-STATE`. As part of replacing `lxc-enter` with `nsenter`, I used a small shell script with `/bin/sh` to change the current process's cgroup to `.lxc`, matching the `lxc-enter` behaviour: https://code.forgejo.org/forgejo/runner/src/commit/6bc95392821624ad79f7bdc7f682bafe372202a0/act/container/host_environment.go#L306-L309 Experimentally, it seems that `/bin/sh` is stripping out the `INPUT_KEEP-STATE` environment variable. This may be considered consistent with its documentation; `/bin/sh` in Debian is implemented by dash, does this: "When starting up, the shell turns all the environment variables into shell variables.", and the POSIX standard for environment variables are that they consist solely of uppercase letters, digits, and underscores, resulting in `/bin/sh` stripping out `INPUT_KEEP-STATE` because it has a dash in it. That causes `setup-buildx` to fail because it's looking for `INPUT_KEEP-STATE` to have a value and it's a required field. I have a fix in hand to replace `/bin/sh` with `/bin/bash` which addresses the bug, and I'm testing it. At the moment, runner v12.6.0 & v12.6.1 are impacted and will fail to pass environment variables and inputs to actions which include a `-` in the name, when using the LXC environment.
viceice-bot changed title from Update https://data.forgejo.org/actions/setup-forgejo action to v3.1.2 to Update https://data.forgejo.org/actions/setup-forgejo action to v3.1.3 2026-01-26 02:33:13 +00:00
viceice-bot force-pushed renovate/https-data.forgejo.org-actions-setup-forgejo-3.x from d3abf08176
Some checks failed
example / docker-build-push-action-in-lxc (pull_request) Successful in 1m49s
Details
checks / Build Forgejo Runner (pull_request) Successful in 1m24s
Details
checks / validate mocks (pull_request) Successful in 1m2s
Details
checks / validate pre-commit-hooks file (pull_request) Successful in 52s
Details
cascade / forgejo (pull_request_target) Has been skipped
Details
cascade / debug (pull_request_target) Has been skipped
Details
/ example-on-demand (pull_request) Successful in 4m38s
Details
/ example-lxc-systemd (pull_request) Successful in 8m25s
Details
checks / Build unsupported platforms (pull_request) Successful in 32s
Details
checks / runner exec tests (pull_request) Successful in 36s
Details
checks / integration tests (docker-latest) (pull_request) Successful in 11m2s
Details
checks / integration tests (docker-stable) (pull_request) Successful in 12m44s
Details
cascade / end-to-end (pull_request_target) Successful in 47m18s
Details
Integration tests for the release process / release-simulation (pull_request) Failing after 3m5s
Details
issue-labels / release-notes (pull_request_target) Has been skipped
Details
to 7285b1b66e
All checks were successful
issue-labels / release-notes (pull_request_target) Has been skipped
Details
checks / validate mocks (pull_request) Successful in 56s
Details
checks / validate pre-commit-hooks file (pull_request) Successful in 55s
Details
checks / Build Forgejo Runner (pull_request) Successful in 1m14s
Details
checks / Build unsupported platforms (pull_request) Successful in 28s
Details
checks / runner exec tests (pull_request) Successful in 34s
Details
Integration tests for the release process / release-simulation (pull_request) Successful in 4m36s
Details
example / docker-build-push-action-in-lxc (pull_request) Successful in 1m24s
Details
checks / integration tests (docker-latest) (pull_request) Successful in 9m43s
Details
/ example-on-demand (pull_request) Successful in 4m0s
Details
checks / integration tests (docker-stable) (pull_request) Successful in 11m34s
Details
/ example-lxc-systemd (pull_request) Successful in 6m33s
Details
cascade / debug (pull_request_target) Has been skipped
Details
cascade / end-to-end (pull_request_target) Successful in 7s
Details
cascade / forgejo (pull_request_target) Successful in 1m54s
Details
2026-01-26 02:33:15 +00:00 Compare
cascading-pr commented 2026-01-26 02:33:33 +00:00
Contributor
Copy link

cascading-pr updated at actions/setup-forgejo#857

cascading-pr updated at https://code.forgejo.org/actions/setup-forgejo/pulls/857
mfenniak approved these changes 2026-01-26 03:16:22 +00:00
mfenniak deleted branch renovate/https-data.forgejo.org-actions-setup-forgejo-3.x 2026-01-26 03:20:21 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
mfenniak
Labels
Clear labels   
FreeBSD

   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Chore

It is no fun but it needs to be done, this is a chore.

  
Kind/DependencyUpdate

for pull requests that are created by renovate when updating a dependency

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Windows

Windows ports is an independent project, see https://github.com/Crown0815/Forgejo-runner-windows-builder

  
linux-powerpc64le

powerpc64le

  
linux-riscv64

   
linux-s390x

   
run-end-to-end-tests

Run https://code.forgejo.org/forgejo/end-to-end with a runner compiled from this pull request

  
run-forgejo-tests

Run https://codeberg.org/forgejo/forgejo tests importing the runner from this pull request

No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
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
forgejo/runner!1331
No description provided.