This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Update WP tag name semantics.#81
Closed
tierra wants to merge 1 commit intoWP-API:masterfrom
tierra:fix-version-check
Closed
Update WP tag name semantics.#81tierra wants to merge 1 commit intoWP-API:masterfrom tierra:fix-version-check
tierra wants to merge 1 commit intoWP-API:masterfrom
tierra:fix-version-check
Conversation
Member
|
We don't need this with change to only master in #76. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Tag name semantics have changed in upstream repo, so using "3.8" now actually checks out the branch rather than the "3.8.0" tag, so this is why the WP version check in the unit tests fail. This should hopefully fix it.