-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update actions/checkout action to v4 #172
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
This change is in preperations to the new Docker Compose configuration changes that are planned for the near future. Currently, the Docker Compose configuration does NOT have persistant storage in the form of Docker Volumes, that will change once the planned updates are pushed. The reason Docker Volumes might have not been possible (or at least difficult) is due to the fact that Whirl-generated files were just thrown about, e.g., `whirl.sqlite3`, `Whirl.toml`, all of these files had no central location so having a shared folder in the form of Docker Volume between the container and the host wasn't very possible.j BREAKING CHANGE: Whirl-generated files are moved to their own directories, if the files are not moved, Whirl will continue to look for these files and panic due to being unable to find them!
Since the configuration file is in the `.whirl` directory, it is redundant to have it's name still as `Whirl.toml` BREAKING CHANGE: Configuration file is renamed
The file name `whirl.sqlite3` is redundant as the file is already in the `.whirl` directory. BREAKING CHANGE: Database file renamed
Previously, Whirl would grab the default configuration data from the the `Default` trait of `Config`, this means that the configuration of a Docker container could not be modified. As well, the database would be reset upon the restart of the Docker container... This solution introduces a shared Volume directory with the label `.whirl-data` which acts as a means of persistant data storage for Whirl.
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] <[email protected]>
…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
chore(deps): update commitlint monorepo to v16.2.1
fix(deps): update rust crate mimalloc to 0.1.28
fix(deps): update rust crate sysinfo to 0.23.5
fix(deps): update rust crate flexi_logger to 0.22.3
fix(deps): update rust crate hyper to 0.14.17
fix(deps): update rust crate serde_derive to 1.0.136
fix(deps): update rust crate serde to 1.0.136
Fuwn
force-pushed
the
renovate/actions-checkout-4.x
branch
from
October 21, 2024 03:43
7e70b94
to
c63dfc2
Compare
Fuwn
force-pushed
the
renovate/actions-checkout-4.x
branch
from
October 21, 2024 03:50
c63dfc2
to
7e70b94
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 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:
v3
->v4
Release Notes
actions/checkout (actions/checkout)
v4
Compare Source
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.