Update to v15.0.3 #54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "upstream"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Forgejo Actions keeps one set of artifacts per workflow run -- those of the latest workflow run. If a particular workflow run is rerun, Forgejo is supposed to remove outdated artifacts. However, it does not do that. As a result, the user is presented a mix of outdated and new artifacts, even within the same archive. This is remedied by wiping the artifacts before each rerun. The same happens when only one or more jobs are rerun, which also matches the behaviour of GitHub Actions. In the example below, when only rerunning `artifacts-two`, `many-artifacts-one` would disappear and a new version of `many-artifacts-two` would be made available. Reproducer: ```yaml on: push: jobs: artifacts-one: runs-on: ubuntu-latest steps: - run: mkdir -p artifacts-one - run: | if [[ "${{ github.run_attempt}}" == 1 ]] ; then echo "${{ github.run_attempt}}" > artifacts-one/ONE; fi echo "${{ github.run_attempt}}" > artifacts-one/TWO - uses: forgejo/upload-artifact@v4 with: name: many-artifacts-one path: artifacts-one/ artifacts-two: runs-on: ubuntu-latest steps: - run: mkdir -p artifacts-two - run: | if [[ "${{ github.run_attempt}}" == 1 ]] ; then echo "${{ github.run_attempt}}" > artifacts-two/ONE; fi echo "${{ github.run_attempt}}" > artifacts-two/TWO - uses: forgejo/upload-artifact@v4 with: name: many-artifacts-two path: artifacts-two/ ``` Resolves https://codeberg.org/forgejo/forgejo/issues/12163. ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. All work and communication must conform to Forgejo's [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md). There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests for Go changes (can be removed for JavaScript changes) - I added test coverage for Go changes... - [ ] in their respective `*_test.go` for unit tests. - [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I ran... - [x] `make pr-go` before pushing ### Tests for JavaScript changes (can be removed for Go changes) - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [x] I did not document these changes and I do not expect someone else to do it. ### Release notes - [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change. - [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change. *The decision if the pull request will be shown in the release notes is up to the mergers / release team.* The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/12523 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org> (cherry picked from commit 753e289da58fd2e1044725f5f4cc42b0818b1d90) Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/12542 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>github.com/robfig/cron/v3(#12365) (#12777) 8ceb69671amake tidy-checkfailure after recent merges (#12780) 30864acb71