Rework CI and justfile#31
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR reworks the CI pipeline and standardizes the justfile to improve adaptability and maintainability across projects.
- Updated justfile recipes for consistent command execution and feature flag usage
- Revised CI workflows and dependabot settings to streamline testing and dependency management
- Minor documentation and YAML format fixes in README and dependabot configuration
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| justfile | Standardizes build, test, and utility commands with new reusable targets |
| README.md | Updates license wording for clarity |
| .github/workflows/dependabot.yml | Updates dependabot metadata usage |
| .github/workflows/ci.yml | Enhances CI flow with added steps for caching, MSRV, and coverage reports |
| .github/dependabot.yml | Refines dependency update configuration |
Comments suppressed due to low confidence (1)
justfile:144
- Consider quoting variables like $COMMAND and $INSTALL_CMD in the cargo-install target to prevent potential word-splitting issues when the command names contain special characters or spaces.
[private] cargo-install $COMMAND $INSTALL_CMD='' *args='':
* Update just recipes to be more standardized and easier to adapt to any other project * update dependabot settings * update CI steps
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
Merged
nyurik
added a commit
that referenced
this pull request
Jun 16, 2025
## 🤖 New release * `tilejson`: 0.4.2 -> 0.4.3 (✓ API compatible changes) <details><summary><i><b>Changelog</b></i></summary><p> <blockquote> ## [0.4.3](v0.4.2...v0.4.3) - 2025-06-16 ### Other - set release-plz CI ([#43](#43)) ([#36](#36)) - minor justfile and precommit adjustments ([#35](#35)) - Ensure create has not been published ([#34](#34)) - ci updates ([#33](#33)) - more ci updates ([#32](#32)) - minor dependabot settings update - Rework CI and justfile ([#31](#31)) - Sort justfiles alphabetically ([#30](#30)) <a name="v0.4.2"></a> ### v0.4.2 (2025-03-03) * Update dependencies, set MSRV to 1.78, and some internal cleanup <a name="v0.4.1"></a> ### v0.4.1 (2022-12-08) * Add `Bounds::from` for `(f64, f64, f64, f64)` tuple. Same for `f32` and `i32`. * Add `Center::from` for `(f64, f64, u8)` and `(f32, f32, u8)` tuples. * A few clippy-related fixes <a name="v0.4.0"></a> ### v0.4.0 (2022-11-19) * Switch all `HashMap` to `BTreeMap` for consistent serialization ordering <a name="v0.3.4"></a> ### v0.3.4 (2022-11-15) * Add proper `Error` implementation to `Bounds` and `Center` parsing errors <a name="v0.3.3"></a> ### v0.3.3 (2022-11-07) * Add `Display` with precision support for `Bounds` and `Center` structs <a name="v0.3.2"></a> ### v0.3.2 (2022-10-30) * Add `Bounds::from` for `[f64; 4]`, `[f32; 4]`, `[i32; 4]` * Add `Bounds::try_from` now also supports `&[f64]`, `&[f32]`, `&[i32]` in addition to `Vec<f64>` <a name="v0.3.1"></a> ### v0.3.1 (2022-05-29) * Add `Bounds::MAX` to create a maximum -180..180, -90..90 value. * Add `Bounds::MAX_TILED` to create a maximum allowed for vector tiles per spec. * Implement `Add` and `AddAssign` on `Bounds` <a name="v0.3.0"></a> ### v0.3.0 (2022-05-25) **ATTENTION:** This release contains many breaking changes. See [README](README.md) for usage examples. * Migrate to Rust 2021 edition * update docs to match v3.0.0 spec * add `fillzoom` field per v3.0.0 spec * add `Center` and `Bounds` structs instead of arrays * both support `FromStr` trait * add `VectorLayer` struct and the `vector_layer` field * Remove builder pattern because `TileJSON` is writable * Add `other` fields for any unknown fields in root and vector layers * Restructure instantiation: * use `tilejson!{ source }` macro to create `TileJSON` objects, with any number of the optional `field: value` pairs. * use `set_missing_defaults()` to replace all missing values with their defaults (only if the spec defines it) * Remove `id` field because it is not supported by the spec <a name="v0.2.4"></a> ### v0.2.4 (2021-10-11) #### Bug Fixes * use String instead of &'static str for `tilejson` field (#7) ([25b325c](25b325c)) <a name="v0.2.3"></a> ### v0.2.3 (2021-10-10) #### Bug Fixes * skip serializing if Option is None (#6) (h/t @jaspervercnocke) ([149339c](149339c)) <a name="0.2.2"></a> ### v0.2.2 (2020-09-12) #### Features * change type of bounds to f32 instead of i32 (#1) (h/t @jaspervercnocke) ([a7cffa8](a7cffa8)) #### Bug Fixes * use crate pub ([09f051a](09f051a)) </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/release-plz/release-plz/).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
- [ ] I added an entry toCHANGES.mdif knowledge of this change could be valuable to users.