console_error_panic_hook
                                
                                 console_error_panic_hook copied to clipboard
                                
                                    console_error_panic_hook copied to clipboard
                            
                            
                            
                        Update cfg-if requirement from 0.1.6 to 1.0.0
⚠️ Dependabot Preview has been deactivated ⚠️
This pull request was created by Dependabot Preview, and you've upgraded to Dependabot. This means it won't respond to dependabot commands nor will it be automatically closed if a new version is found.
If you close this pull request, Dependabot will re-create it the next time it checks for updates and everything will work as expected.
Updates the requirements on cfg-if to permit the latest version.
Commits
- e60fa1eBump to 1.0.0
- 7daa598Prohibit multiple predicates (#37)
- f71bf60Another attempt at gh-pages
- f779d28Change push username for gh-pages
- 4484a6fBump to 0.1.10
- a625fbeAdd a test for the body of an- impl
- 33a8869Merge pull request #28 from Lokathor/token-trees
- 571a28dremove the __apply internal macro
- 75e817fadjust the test
- 3e9d487notes fix
- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
If all status checks pass Dependabot will automatically merge this pull request.
Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking Bump now in your Dependabot dashboard.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- @dependabot rebasewill rebase this PR
- @dependabot recreatewill recreate this PR, overwriting any edits that have been made to it
- @dependabot mergewill merge this PR after your CI passes on it
- @dependabot squash and mergewill squash and merge this PR after your CI passes on it
- @dependabot cancel mergewill cancel a previously requested merge and block automerging
- @dependabot reopenwill reopen this PR if it is closed
- @dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- @dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- @dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- @dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- @dependabot use these labelswill set the current labels as the default for future PRs for this repo and language
- @dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language
- @dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language
- @dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
- @dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
I'm getting cargo deny check from this not being updated, not sure if there is anything that needs to be tested/checked here before this is merged
@fitzgen ping
It seems like cfg-if is a purely internal dependency, there is absolutely no reason to update that from a user's perspective, right? Unless there is some security consideration in the version of cfg-if used..