Skip to content
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

feat: change name so we push up to crates.io #1

Merged
merged 2 commits into from
Feb 9, 2024
Merged

Conversation

SWvheerden
Copy link

Changes the name of this fork to tari_log4rs so we can push this up to crates.io

@SWvheerden SWvheerden merged commit ddd52a4 into master Feb 9, 2024
SWvheerden pushed a commit to tari-project/tari that referenced this pull request Feb 15, 2024
Description
---
Switch to log4rs 1.3

Motivation and Context
---
tari-project/log4rs#1
estk/log4rs#345

It appears that the log4rs commits arent used since the cargo.lock rev
was set to commit
[`e1051fd3a1bec9c55d055f60176a96cf11e58505`](tari-project/log4rs@e1051fd)
https://github.com/tari-project/log4rs/commits/master/#:r3d:-listview-node-:r3e:
and the crate was renamed to tari_log4rs. This rename will only break
the current build if the cargo.lock is updated. Since no rev or tag is
used, current `master` would be used.

@SWvheerden Please verify the changes are in log4rs@1.3 that were
required. Just this right?
https://github.com/estk/log4rs/blob/c981ca4e2126c5728505c562b34926f9a9fad00b/Cargo.toml#L59

Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->
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.

1 participant