Skip to content

Conversation

@kesselb
Copy link
Contributor

@kesselb kesselb commented Jan 20, 2026

Please review carefully, as I'm not so familiar with the CI over here ⚠️

a214571 is optional. We are doing the same in mail to avoid unnecessary action bumps since nextcloud/mail#12137

@SebastianKrupinski
Copy link
Contributor

Duplicate of #5013

@SebastianKrupinski SebastianKrupinski marked this as a duplicate of #5013 Jan 20, 2026
@codecov
Copy link

codecov bot commented Jan 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@SebastianKrupinski
Copy link
Contributor

Also can we make the appstore-build-publish.yml a separate PR this has to be independently tested and if it needs to be reversed it will be easier to reverse

@kesselb
Copy link
Contributor Author

kesselb commented Jan 20, 2026

It appears that David missed a couple of changes in #5013?

Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
renovate.json Outdated
Comment on lines 35 to 54
"ignorePaths": [
".github/workflows/appstore-build-publish.yml",
".github/workflows/appstore-conventional-build-publish.yml",
".github/workflows/block-unconventional-commits.yml",
".github/workflows/fixup.yml",
".github/workflows/lint-eslint.yml",
".github/workflows/lint-eslint-when-unrelated.yml",
".github/workflows/lint-info-xml.yml",
".github/workflows/lint-php-cs.yml",
".github/workflows/lint-php.yml",
".github/workflows/lint-stylelint.yml",
".github/workflows/node-test.yml",
".github/workflows/node.yml",
".github/workflows/npm-audit-fix.yml",
".github/workflows/npm-audit-fix-selective.yml",
".github/workflows/openapi.yml",
".github/workflows/pr-feedback.yml",
".github/workflows/psalm-matrix.yml",
".github/workflows/reuse.yml"
],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we want to ignore the workflows? I use renovate to updated these all the time

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That commit is optional. Those workflows are maintained at nextcloud/mail#12137. Having renovate and update them leads to the state that they are out of sync. That's probably not an issue, but also unnecessary work. What we do in mail is to update only the "local" workflows by renovate, and update the workflows from the template (with that script from over there) every here and then. Let me know if you want me to drop that commit, and you continue to update those workflow actions by renovate.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets drop the renovate ignores... The workflows only need to be updated once a year... but the actions should be updated on a regular basis... and automating it is just much easier then running a manual update here and there

@SebastianKrupinski
Copy link
Contributor

SebastianKrupinski commented Jan 20, 2026

The new node.yml is failing... why do we need node.yml and node-test.yml?

Looks like node.yml just does a build test... and so does node-test.yml

@kesselb
Copy link
Contributor Author

kesselb commented Jan 20, 2026

The new node.yml is failing...

Looking at nextcloud/.github#620 and nextcloud/photos#3178 it seems that the lockfile is not up-to-date. I'm running npx npm-package-lock-add-resolved right now and will commit the result when it's done.

why do we need node.yml and node-test.yml?

I don't know, probably there are there for historical reasons. That validation step, package lock ok/nok, is currently only available in node.yml though.

…k.json

Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
@SebastianKrupinski SebastianKrupinski merged commit f2edd0f into main Jan 20, 2026
78 of 80 checks passed
@SebastianKrupinski SebastianKrupinski deleted the update-workflows branch January 20, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants