ci: Remove Fedora packaging workflow #1924

Merged

ginger merged 1 commit from julian45/continuwuity:julian/nuke-cicd-fedora into main 2026-07-09 18:40:56 +00:00

Conversation 4 Commits 1 Files changed 1 -394

julian45 commented 2026-07-07 18:13:37 +00:00

Member

Copy link

This pull request removes the Fedora packaging and publishing workflow from CI. Said workflow is no longer required, as Terra now distributes both stable-release and nightly packages, including for EL-family distros as well.
(I just fixed an issue with the continuwuity-nightly update process in Terra this morning, so I'll keep this PR in WIP until I confirm after a nightly run that new nightlies are in fact being built & distributed. Later edit: Terra stuff has been sorted out :3)

The intent is for this PR to be merged prior to the next stable release. This will require drawing some attention in the release notes, but it forces RPM deployers to make the change in order to update.
Other options discussed but dismissed included:

• "Copying" the latest release from Terra's repo to ours (straight RPM copying would generate errors for deployers due to RPM signing key mismatches; rebuilding from the SRPM in our CI would require significant futzing with this workflow to install Terra-specific build toolchain and RPM macros that aren't worth the trouble)
• Letting this workflow stick around until after the next release (doesn't generate sufficient justification to make the upgrade)

Pull request checklist:

• This pull request targets the main branch, and the branch is named something other than
  main.
• I have written an appropriate pull request title and my description is clear.
• I understand I am responsible for the contents of this pull request.
• I have followed the contributing guidelines:
  • My contribution follows the code style, if applicable.
  • I ran pre-commit checks before opening/drafting this pull request.
  • I have tested my contribution (or proof-read it for documentation-only changes)
    myself, if applicable. This includes ensuring code compiles.
  • My commit messages follow the commit message format and are descriptive.

<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> This pull request removes the Fedora packaging and publishing workflow from CI. Said workflow is no longer required, as Terra now distributes both stable-release and nightly packages, including for EL-family distros as well. (~~I just fixed an issue with the continuwuity-nightly update process in Terra this morning, so I'll keep this PR in WIP until I confirm after a nightly run that new nightlies are in fact being built & distributed.~~ Later edit: Terra stuff has been sorted out :3) **The intent is for this PR to be merged *prior* to the next stable release.** This will require drawing some attention in the release notes, but it forces RPM deployers to make the change in order to update. Other options [discussed](matrix:roomid/ksTlboXVgcyWjv5GrlEeKyQuJ8ZCprnwQx2b6-BQ44Q/e/491vMyoJILkhFka6fwPkT01x873sBTQ4YIbPjFrzDzw?via=julian45.net&via=explodie.org&via=federated.nexus) but dismissed included: - "Copying" the latest release from Terra's repo to ours (straight RPM copying would generate errors for deployers due to RPM signing key mismatches; rebuilding from the SRPM in our CI would require significant futzing with this workflow to install Terra-specific build toolchain and RPM macros that aren't worth the trouble) - Letting this workflow stick around until after the next release (doesn't generate sufficient justification to make the upgrade) <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages

julian45 added 1 commit 2026-07-07 18:13:37 +00:00

ci: Remove Fedora packaging workflow ... 065914a0fe

No longer needed because Terra now distributes both stable and nightly
releases for Fedora- & EL-family distributions.

forgejo-actions added the

Meta/CI

label 2026-07-07 18:13:40 +00:00

stratself commented 2026-07-08 19:27:30 +00:00

Contributor

Copy link

This should get its own changelog.d

This should get its own changelog.d

julian45 commented 2026-07-08 20:23:16 +00:00

Author

Member

Copy link

@stratself wrote in #1924 (comment):

This should get its own changelog.d

Should it, though? By our contributing guide and CI checks, removal of a CI workflow alone doesn’t inherently warrant a changelog.d entry. I did say when opening the PR (and also in the dev room too) that attention would need to be drawn in the release notes to make sure prior users of these packages make the switch to Terra, but that can be done in the freeform part above changelog entries.
That said, if it is decided that it warrants a changelog entry, I suppose that out of the types enumerated in the contributing guide, it’d be misc?

@stratself wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/1924#issuecomment-31436: > This should get its own changelog.d Should it, though? By our contributing guide and CI checks, removal of a CI workflow alone doesn’t inherently warrant a changelog.d entry. I *did* say when opening the PR (and also in the dev room too) that attention would need to be drawn in the release notes to make sure prior users of these packages make the switch to Terra, but that can be done in the freeform part above changelog entries. That said, if it *is* decided that it warrants a changelog entry, I suppose that out of the types enumerated in the contributing guide, it’d be `misc`?

stratself commented 2026-07-08 20:34:17 +00:00

Contributor

Copy link

I agree the freeform could be used, but it could miss out on some entries. Having inline report of significant removals would make it more complete, and allow for contribs to explain the breaking effect of their changes too. This is also inline with other projects like Codeberg changelogs

If it were me I'd likely do it as such:

ci: Remove Fedora packages. **Breaking**: Fedora packages will mot be provided on the forge - use Terra instead. Contributed by @julian45

Maintainers have final discretion tho

I agree the freeform could be used, but it could miss out on some entries. Having inline report of significant removals would make it more complete, and allow for contribs to explain the breaking effect of their changes too. This is also inline with other projects like [Codeberg changelogs](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/15.0.0.md) If it were me I'd likely do it as such: ``` ci: Remove Fedora packages. **Breaking**: Fedora packages will mot be provided on the forge - use Terra instead. Contributed by @julian45 ``` Maintainers have final discretion tho

ginger changed title from WIP: ci: Remove Fedora packaging workflow to ci: Remove Fedora packaging workflow 2026-07-09 18:12:25 +00:00

ginger added this to the 26.6.0 milestone 2026-07-09 18:12:29 +00:00

ginger changed title from ci: Remove Fedora packaging workflow to WIP: ci: Remove Fedora packaging workflow 2026-07-09 18:15:19 +00:00

julian45 changed title from WIP: ci: Remove Fedora packaging workflow to ci: Remove Fedora packaging workflow 2026-07-09 18:40:09 +00:00

ginger approved these changes 2026-07-09 18:40:37 +00:00

julian45 force-pushed julian/nuke-cicd-fedora from 065914a0fe to 3ad229a2bc 2026-07-09 18:40:44 +00:00 Compare

ginger merged commit 3ad229a2bc into main 2026-07-09 18:40:56 +00:00

julian45 deleted branch julian/nuke-cicd-fedora 2026-07-09 18:47:03 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

ginger

Labels

Clear labels   

Abandoned

This pull request appears to be abandoned by its author.

  

Blocked

This pull request or issue is currently blocked from being merged/closed

  

Bug

Something isn't working as intended

  

Changelog

Added

Changelog entry added

  

Changelog

Missing

No changelog when one is needed

  

Changelog

None

Changelog is unnecesary for this change

  

Cherry-picking

Commits picked from other conduit projects

  

Database

This requires or includes changes to the database

  

Dependencies

Something dependency related

  

Dependencies/Renovate

Automatic dependency upgrades by Renovate

  

Difficulty

Easy

Low difficulty to implement - touches few parts of the codebase, low complexity

  

Difficulty

Hard

High difficulty to implement - touches many parts of the codebase, high complexity

  

Difficulty

Medium

Medium difficulty to implement - touches more parts of the codebase, higher complexity

  

Documentation

Improvements or additions to documentation

  

Enhancement

New feature or request

  

Good first issue

Good for newcomers

  

Help wanted

Additional eyes and keyboards are required for this one

  

Inherited

Issues that have been inhereted from the project pre-fork

  

Matrix/Administration

Features pertaining to homeserver administration

  

Matrix/Appservices

Features pertaining to the appservice API

  

Matrix/Auth

Features pertaining to authentication

  

Matrix/Client

Features pertaining to client-to-server interactions

  

Matrix/Core

Issues relating to core matrix functionality, such as state resolution and PDU formats

  

Matrix/E2EE

Issues related to end to end encryption

  

Matrix/Federation

Features pertaining to server-to-server interactions

  

Matrix/Hydra

Issues related to room version 12 and related changes (temporary label)

  

Matrix/MSC

Features pertaining to unstable matrix features

  

Matrix/Media

Features pertaining to media interactions

  

Matrix/T&S

Changes or issues related to trust & safety tooling

  

Merge

This PR is ready to be merged

  

Merge/Manual

This PR should be manually merged

  

Merge/Squash

This PR should be squashed when it is merged

  

Meta

Related to housekeeping, maintenance, or other repo-meta.

  

Meta/CI

Issues related to CI changes

  

Meta/Packaging

Packaging

  

Priority

Blocking

This issue is blocking the next release

  

Priority

High

This issue is very important

  

Priority

Low

This issue is of a rather low priority

  

Security

This item is related to general security

  

Status

Confirmed

This issue has enough information and is confirmed

  

Status

Duplicate

This issue or pull request already exists

  

Status

Invalid

This issue doesn't seem right

  

Status

Needs Investigation

This issue needs further investigation

  

Support

Questions or support requests

No labels

Abandoned

Blocked

Bug

Changelog

Added

Changelog

Missing

Changelog

None

Cherry-picking

Database

Dependencies

Dependencies/Renovate

Difficulty

Easy

Difficulty

Hard

Difficulty

Medium

Documentation

Enhancement

Good first issue

Help wanted

Inherited

Matrix/Administration

Matrix/Appservices

Matrix/Auth

Matrix/Client

Matrix/Core

Matrix/E2EE

Matrix/Federation

Matrix/Hydra

Matrix/MSC

Matrix/Media

Matrix/T&S

Merge

Merge/Manual

Merge/Squash

Meta

Meta/CI

Meta/Packaging

Priority

Blocking

Priority

High

Priority

Low

Security

Status

Confirmed

Status

Duplicate

Status

Invalid

Status

Needs Investigation

Support

Milestone

Clear milestone

No items

No milestone

26.6.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Notifications

Subscribe

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

continuwuation/continuwuity!1924

No description provided.