-
Notifications
You must be signed in to change notification settings - Fork 15
release: v2.1.2 #179
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
Merged
Merged
release: v2.1.2 #179
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
Bumps the composer group with 1 update in the /. directory: [composer/composer](https://github.com/composer/composer). Updates `composer/composer` from 2.2.22 to 2.2.23 - [Release notes](https://github.com/composer/composer/releases) - [Changelog](https://github.com/composer/composer/blob/main/CHANGELOG.md) - [Commits](composer/composer@2.2.22...2.2.23) --- updated-dependencies: - dependency-name: composer/composer dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…composer-2.2.23 Bump the composer group across 1 directories with 1 update
Update bug_report.yml
…s are saved - update taxonomy field resolver to se the default order and orderby when resolving with the TermObjectConnectionResolver
…es-wrong-order fix: taxonomy field resolves with wrong order
…esolver returns incorrect information. This resolves that by accounting for IDs or Objects being stored and returned.
…taxonomy-field-not-handling-objects-properly
…ect vs id & array vs individual value) - add test for Taxonomy field when 'object' is set as the return type
…ndling-objects-properly fix: Taxonomy field returns incorrect data if set to store objects instead of IDs
Pull Request Test Coverage Report for Build b9426d1282e569e55f671a0b4a29e3fbf01fb837-PR-179Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
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.
Release Notes
Chores / Bugfixes