Opened 9 years ago
Closed 9 years ago
#36845 closed defect (bug) (fixed)
Bump $wp_version to the latest revision number
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.6 | Priority: | normal |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
Could someone bump $wp_version
to the latest revision number?
It's currently at r37183 from 5 weeks ago.
Change History (4)
#2
@
9 years ago
- Keywords close removed
For context, I'm assuming this is related to Requests landing in Core and WP CLI needing to selectively include the new file(s) . WP-CLI selectively includes things based on wp_version number, e.g. https://github.com/kraftbj/wp-cli/blob/47aa5229c8b860849a2f0d9a054008891874be53/php/wp-settings-cli.php#L171
The bump is helpful for running WP CLI and various possible states of trunk on our servers. :-)
IIRC, r35088 was done to help with this after the embed-functions.php was added in the 4.4 cycle.
#3
@
9 years ago
Yup, I've just read the Slack chat logs: https://wordpress.slack.com/archives/core/p1463329620004965
Including either a link to the chat log or the addition of that related information for context would have been helpful.
Based on the Slack chat logs now there are two options: 1. Bump the version or 2. Use a file exists check
This is correct, you can see the revision logs for when the version is typically bumped:
https://core.trac.wordpress.org/log/trunk/src/wp-includes/version.php
For the
build.svn
repo it is the current commit4.6-alpha-37435
per the latestcore.svn
commit r37435:https://build.trac.wordpress.org/browser/trunk/wp-includes/version.php#L7