Skip to content
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

Release version 1.0.1 #44

Merged
merged 20 commits into from
Jun 28, 2020
Merged

Release version 1.0.1 #44

merged 20 commits into from
Jun 28, 2020

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented Jun 28, 2020

Release checklist:

  • Update the version number in the VERSION file. PR Update the version nr for the release #43
  • Add changelog for 1.0.1 - PR Readme/Changelog: update for release of v 1.0.1 #42
  • Merge this PR
  • Add release tag against stable (careful, GH defaults to develop!) & copy & paste the changelog to it
  • Close the milestone
  • Open a new milestone for the next release
  • If any open PRs/issues which were milestoned for this release did not make it into the release, update their milestone. (not applicable)
  • Tweet about the release.
  • Fast-forward develop to stable & push it.

jrfnl and others added 20 commits March 10, 2020 01:37
... as the original appears not to be maintained anymore and is not compatible with PHP 7.4.
…fork

CI: switch to fork of Parallel-lint package
The Travis docs say that `$TRAVIS_BUILD_STAGE_NAME` is in "proper case" form:

> TRAVIS_BUILD_STAGE_NAME: The build stage in capitalized form, e.g. Test or Deploy. If a build does not use build stages, this variable is empty ("").

However, it looks like they made an (undocumented) change (probably a bug in their script handling) which means that the `$TRAVIS_BUILD_STAGE_NAME` name is now in the case as given, which in this case is _lowercase_.

This means that some of the comparisons are failing and the wrong things are executed for certain builds.

As I expect this to be a bug in Travis, I'm not changing the case for the comparisons at this time.
Instead I'm fixing this by inline fixing the case of the variable for the comparisons.

Refs:
* https://docs.travis-ci.com/user/environment-variables#default-environment-variables (near the bottom of the list)
…4.1`

Support for the `installed_paths` being set when the plugin is a requirement of a standard itself, was only added in version `0.4.0` and a pertinent bug in this feature was fixed in `0.4.1`, which effectively makes version `0.4.1` the minimum workable version for both use as a stand-alone standard, as well as when this standard is required as a dependency.

Refs:
* https://github.com/Dealerdirect/phpcodesniffer-composer-installer/releases/tag/v0.4.0
* https://github.com/Dealerdirect/phpcodesniffer-composer-installer/releases/tag/v0.4.1
Remove some duplication.
…-plugin-dependency

Composer: set minimum Composer PHPCS plugin dependency version to `0.4.1`
The DealerDirect Composer plugin has just released version `0.7.0`.
As Composer treats minors < 1.0 as majors, updating to this version requires an update to the `composer.json` requirements.

> For pre-1.0 versions it also acts with safety in mind and treats `^0.3` as `>=0.3.0 <0.4.0`.

Refs:
* https://github.com/Dealerdirect/phpcodesniffer-composer-installer/releases/tag/v0.7.0
* https://getcomposer.org/doc/articles/versions.md#caret-version-range-
…oser-plugin-version

Composer: update PHPCS Composer plugin dependency
* Run the sniff build against PHP 7.4.
* Add a new build on PHP 7.4 to test against PHPCS 4.x.
* Enable running the unit tests on PHP nightly (8.0).
* Tweak the installation conditions to allow the builds to run & potentially pass.
…phpcs-4.x

Travis: add testing against PHPCS 4.x and other tweaks
* Update the branch conditions for the Travis script.
* Update the badges in the Readme.
…table

Misc updates for the `master` branch being renamed to `stable`
…release

Readme/Changelog: update for release of v 1.0.1
@jrfnl jrfnl added this to the 1.0.1 milestone Jun 28, 2020
@jrfnl jrfnl merged commit 5cb7f67 into stable Jun 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant