Skip to content

Metadata: Add missing repository information#43451

Merged
TimvdLippe merged 1 commit into
servo:mainfrom
jschwe:metadata
Mar 19, 2026
Merged

Metadata: Add missing repository information#43451
TimvdLippe merged 1 commit into
servo:mainfrom
jschwe:metadata

Conversation

@jschwe

@jschwe jschwe commented Mar 19, 2026

Copy link
Copy Markdown
Member

This fixes a warning of cargo publish:

warning: manifest has no description, documentation, homepage or repository

Testing: Compiling. Manual testing of cargo publish --dry-run (with some additional patches, and until the next error, shows this warning has been fixed)

Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
@servo-highfive servo-highfive added the S-awaiting-review There is new code that needs to be reviewed. label Mar 19, 2026
@servo-highfive servo-highfive removed the S-awaiting-review There is new code that needs to be reviewed. label Mar 19, 2026
@TimvdLippe TimvdLippe enabled auto-merge March 19, 2026 08:47
@TimvdLippe TimvdLippe added this pull request to the merge queue Mar 19, 2026
@servo-highfive servo-highfive added the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Mar 19, 2026
Merged via the queue into servo:main with commit eac6ff8 Mar 19, 2026
33 checks passed
@servo-highfive servo-highfive removed the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Mar 19, 2026
@jschwe jschwe deleted the metadata branch March 19, 2026 09:47
github-merge-queue Bot pushed a commit that referenced this pull request Mar 19, 2026
Add further missing repository keys / descriptions, which I missed in
#43451 due to a suboptimal grep (assuming that rust-version.workspace is
always the last item).
Additionally fix crate self-references, which caused cargo-publish to
fail, due to it trying to fetch the crate from crates.io.
When specifying the current crate in `[dev-dependencies]` to enable a
test feature or similar, apparently one should not use `workspace =
true` and instead use `path`.
This requires extending the previously added `tidy` check, to allow
`path` dependencies in this specific case outside of the workspace
Cargo.toml.

Testing: Covered by existing tests

---------

Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
Gae24 pushed a commit to Gae24/servo that referenced this pull request Mar 26, 2026
This fixes a warning of `cargo publish`: 

```
warning: manifest has no description, documentation, homepage or repository
```

Testing: Compiling. Manual testing of `cargo publish --dry-run` (with
some additional patches, and until the next error, shows this warning
has been fixed)

Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
Gae24 pushed a commit to Gae24/servo that referenced this pull request Mar 26, 2026
Add further missing repository keys / descriptions, which I missed in
servo#43451 due to a suboptimal grep (assuming that rust-version.workspace is
always the last item).
Additionally fix crate self-references, which caused cargo-publish to
fail, due to it trying to fetch the crate from crates.io.
When specifying the current crate in `[dev-dependencies]` to enable a
test feature or similar, apparently one should not use `workspace =
true` and instead use `path`.
This requires extending the previously added `tidy` check, to allow
`path` dependencies in this specific case outside of the workspace
Cargo.toml.

Testing: Covered by existing tests

---------

Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
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