fix: Update package and crate metadata #1259

Merged
ginger merged 2 commits from ginger/update-metadata into main 2026-01-08 19:28:28 +00:00
Owner

This pull request updates the project metadata in Cargo.toml and the packaging files to be consistent with each other.

<!-- 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 updates the project metadata in Cargo.toml and the packaging files to be consistent with each other. <!-- 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`. --> <!-- 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 [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
fix: Update package and crate metadata
Some checks are pending
Documentation / Build and Deploy Documentation (pull_request) Waiting to run
Checks / Prek / Pre-commit & Formatting (pull_request) Waiting to run
Checks / Prek / Clippy and Cargo Tests (pull_request) Waiting to run
Update flake hashes / update-flake-hashes (pull_request) Waiting to run
7f8a76d405
ginger force-pushed ginger/update-metadata from 7f8a76d405
Some checks are pending
Documentation / Build and Deploy Documentation (pull_request) Waiting to run
Checks / Prek / Pre-commit & Formatting (pull_request) Waiting to run
Checks / Prek / Clippy and Cargo Tests (pull_request) Waiting to run
Update flake hashes / update-flake-hashes (pull_request) Waiting to run
to bf37b425be
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m21s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 2m1s
Update flake hashes / update-flake-hashes (pull_request) Successful in 46s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 22m26s
2025-12-31 20:08:00 +00:00
Compare
ginger added this to the 0.6.0 milestone 2026-01-07 17:28:22 +00:00
ginger modified the milestone from 0.6.0 to 0.5.2 2026-01-07 17:28:24 +00:00
ginger force-pushed ginger/update-metadata from 7f8a76d405
Some checks are pending
Documentation / Build and Deploy Documentation (pull_request) Waiting to run
Checks / Prek / Pre-commit & Formatting (pull_request) Waiting to run
Checks / Prek / Clippy and Cargo Tests (pull_request) Waiting to run
Update flake hashes / update-flake-hashes (pull_request) Waiting to run
to 8db8758cf7
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m49s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m14s
Update flake hashes / update-flake-hashes (pull_request) Successful in 2m31s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 26m53s
2026-01-07 17:28:49 +00:00
Compare
Jade approved these changes 2026-01-07 23:17:51 +00:00
Cargo.toml Outdated
@ -14,2 +7,2 @@
categories = ["network-programming"]
description = "a very cool Matrix chat homeserver written in Rust"
authors = ["Continuwuity Team and contributors <team@continuwuity.org>"]
description = "A Matrix homeserver written in Rust, the official continuation of the conduwuit homeserver."
Owner

We really need to decide on an actual tagline

We really need to decide on an actual tagline
ginger force-pushed ginger/update-metadata from 8db8758cf7
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m49s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m14s
Update flake hashes / update-flake-hashes (pull_request) Successful in 2m31s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 26m53s
to 71a26e433f
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Successful in 2m28s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m15s
Update flake hashes / update-flake-hashes (pull_request) Successful in 48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 29m53s
2026-01-08 00:21:29 +00:00
Compare
ginger scheduled this pull request to auto merge when all checks succeed 2026-01-08 00:21:39 +00:00
ginger canceled auto merging this pull request when all checks succeed 2026-01-08 00:21:45 +00:00
ginger scheduled this pull request to auto merge when all checks succeed 2026-01-08 00:21:53 +00:00
fix: Allow cargo_common_metadata clippy lint
All checks were successful
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m10s
Documentation / Build and Deploy Documentation (pull_request) Successful in 2m6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m22s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 30m48s
e5b11af3e8
ginger merged commit d48cc46643 into main 2026-01-08 19:28:28 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 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
continuwuation/continuwuity!1259
No description provided.