New version of flarum/core (1.8.12) broke the build #36
Conversation
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.
We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of flarum/core for this test run.
What changed?
✳️ flarum/core (^1.8 → 1.8.12) · Repo · Changelog
Release Notes
1.8.12
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
chore: update CHANGLOGBundled output for commit edf3e67667d04ceb13f5d6a7bcca7e510f7b53f0[1.x] [suspend] chore: build typings (#4337)fix: php warnings in restricted environments (#4336)[1.x] chore: prep 1.8.12 release (#4335)Bundled output for commit 38e9192c82b0d303bc2dd8d3f6724764ecb8b243[1.x] feat: highlight abandoned packages, expose php flarum info to admin UI (#4322)Bundled output for commit 9b28a9a775aa4a65e9e1c7d642b0603bbc7ef81bfeat(core): allow to disable slidable on `DiscussionListItem` (#4302)fix: peg composer at 2.8.x to avoid security blocking, etc in 2.9 (#4294)[1.x] fix(tags): defer policy if min primary & secondary tags 0 (#4277)Bundled output for commit bf9442f5e5be53e98dca78a3a3082421f42cc3d4chore: update schedule link (#4278)Bundled output for commit 58692be4756e85ecbcd56be74f7312e035a1c4f4fix: don't see developer tokens if not within the first 20 results (#4264)fix(core): restore `xdebug.max_nesting_level` after less compilation (#4262)