fix(deps): update rust crate colour to 0.7.0 #167
Closed
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Bumps [trim-newlines](https://github.com/sindresorhus/trim-newlines) from 3.0.0 to 3.0.1. - [Release notes](https://github.com/sindresorhus/trim-newlines/releases) - [Commits](https://github.com/sindresorhus/trim-newlines/commits) --- updated-dependencies: - dependency-name: trim-newlines dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…newlines-3.0.1
`flexi_logger` version `0.18.0` broke a lot of stuff, this fixes those broken things.
fix(deps): update rust crate flexi_logger to 0.18.0
Instead of being given the option to start all of the sub-servers (`whirl run` or `whirl run all`), you are now given the option to specify a selection of sub-servers by passing a comma-seperated list to the `run` sub-command (`whirl run distributor,hub`). Despite the changes, `whirl run` still starts all of the available sub-servers!
fix(deps): update rust crate tokio to 1.6.2
I guess at some point I accidentally inserted a newline to the end of the `.license_template` file, don't know how I didn't notice until now but this commit fixes the errors that rustfmt would report.
fix(deps): update rust crate tokio to 1.7.0
Issue came back, reverted commit, issue is gone...
At the moment, the `version` key is never accessed, but once Whirl's "`1.0`" release is out, the configuration schema will need to be standardized, the `version` key will regulate that and also ensure no one is left behind when updating. BREAKING CHANGE: `version` key is created
fix(deps): update rust crate mimalloc to 0.1.26
fix(deps): update rust crate serde to 1.0.136
renovate
bot
force-pushed
the
renovate/colour-0.x
branch
from
4f2466c
to
36fcc6f
Compare
Fuwn
force-pushed
the
renovate/colour-0.x
branch
from
36fcc6f
to
2d55be6
Compare
Fuwn
force-pushed
the
renovate/colour-0.x
branch
from
2d55be6
to
36fcc6f
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
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.
This PR contains the following updates:
0.6.0->0.7.0Release Notes
Fraser999/Colour (colour)
v0.7.0Compare Source
Changed
crosstermversion.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.