Update autoprefixer 10.4.19 → 10.4.22 (patch) - #64
Closed
depfu[bot] wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Closed in favor of #65. |
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ autoprefixer (10.4.19 → 10.4.22) · Repo · Changelog
Release Notes
10.4.22
10.4.21
10.4.20
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
Release 10.4.22 versionLock CI action versionsFix Node.js 10 on CIFix old Node.js CIUpdate fraction.jsUpdate dependencies and fix stretch and update exampleRelease 10.4.21 versionUpdate dependencies and sort importsUpdate Node.js and pnpm on CIfix: replace `:-moz-placeholder-shown` with `:-moz-placeholder` (#1532)Release 10.4.20 versionFix fit-content for FirefoxUpdate dependenciesMove to pnpm 9Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by 2 commits:
1.5.250generate new versionCommits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
1.1.1
1.1.0
1.0.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
picocolors@1.1.1Add chalk v5 and yoctocolors to benchmarks (#88)Rework color detection (#87)fix: usage of `node12` in `testing.yaml` (#73)Use mitata, esbuild for benchmarking speed and size (#86)fix(types): move types declaration into "real" types declaration file (.d.ts) (#82)picocolors@1.1.0test: add test (shouldn't overflow when coloring already colored large text) (#74)feat: bright colors variants (#55)miscv1.0.1fix: iteratively replace "close" to avoid maximum stack error (#64)Fix color detection in edge runtime (#56)uniform api usage in complex benchmarkupdate benchmarks per recent job runCreate .gitignore (#37)Release Notes
1.1.4
1.1.3
1.1.2
1.1.1
1.0.16
1.0.15
1.0.14
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 68 commits:
Release 1.1.4 versionPrevent updating package.json on pnpm updateFix old Node.js supportPin CI actionsUpdate Node.js version on CIUpdate dependenciesAdd security sectionMerge pull request #63 from brabli/mainSpecify "latest" argUpdate README.mdRelease 1.1.3 versionUpdate dependenciesAdd new bun lock fileFix pnpm versionRelease 1.1.2 versionLess agressive browsers diff errorUpdate dependenciesUpdate Node.js and pnpm on CIRelease 1.1.1 versionUpdate dependenciesFix typesRelease 1.1 versionUpdate CI actionsUpdate dependenciesAllow to run tests without yarn and bunFix merge conflictClean up codeClean up codeMerge pull request #41 from kytta/25-bunMerge branch 'main' into 25-bunRemove dev tool from dependenciesMerge pull request #40 from pornoiya/feat/bun-supportFix property orderingBun to package.jsonPrettifyAdd Bun to GitHub actionsAdd testsBun support for update-browserslist-dbAdd support for BunMerge pull request #38 from gekkedev/patch-1doc: typo/grammar corrections in the READMERelease 1.0.16 versionRemove node: protocol to support Node.js 14Update dependenciesRelease 1.0.15 versionImprove error message on missed browserslistRelease 1.0.14 versionUpdate dependenciesMerge pull request #34 from mralaminahamed/mainremove: unwanted semicolon from function callremove: PHPStorm ide config from gitignore fileFeat(yarn-detection): detect the presence of yarn and hadoop installationsDisable Yarn 2+ test for old Node.jsUpdate CIFix workflowAdd Node.js 22 to CIAdd GitHub Releases supportRemove debug codeFix tests for new pnpmUpdate ESLint to flat configRevert yarn changes since they faaling testsUpdate dependenciesMove to pnpm 9Fix ESLint warningsMerge pull request #32 from mralaminahamed/mainfix: Command failed: yarnpkg npm info caniuse-lite --jsonMerge pull request #31 from romanlex/patch-1Change text for old version of npm🆕 baseline-browser-mapping (added, 2.8.26)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands