Browse Source

chore: bump version to 0.4.1

merge-requests/13/head 0.4.1
JamesRezo 1 year ago
parent
commit
831407faff
  1. 13
      CHANGELOG
  2. 91
      CONTRIBUTING.md
  3. 4
      README.md
  4. 2
      paquet.xml

13
CHANGELOG

@ -3,14 +3,25 @@
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and
[Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
## [Unreleased]
## [0.4.1] - 2021-05-18
### Added
- `<supportedversions|stable`> model
- Arabic translation
- `|SupportedVersions::getBranchValues` filter
- CI/CD [PHPStan](https://phpstan.org/) dev tool
- [Contributing](CONTRIBUTING.md) file
### Changed
- PHP7.2 minimum version is required
- `not-planned` state in `|SupportedVersions::state` filter if an empty initial_release date is given
## [0.4.0] - 2021-05-16

91
CONTRIBUTING.md

@ -0,0 +1,91 @@
# Contributing
When contributing to this repository, please first discuss the change you wish to make via issue,
email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
## Pull Request Process
1. Update the CHANGELOG and README.md with details of changes to the interface, this includes new filters, models, etc.
2. Increase the version numbers in any examples files and the CHANGELOG to the new version that this
Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
3. You may merge the Pull Request in once you have the sign-off of at least one other developer, or if you
do not have permission to do that, you may request a second reviewer to merge it for you.
## Contributor Covenant Code of Conduct
### Our Pledge
We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual identity
and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.
### Our Standards
Examples of behavior that contributes to a positive environment for our
community include:
* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community
Examples of unacceptable behavior include:
* The use of sexualized language or imagery, and sexual attention or
advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
### Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.
Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.
### Scope
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
### Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
at [https://www.contributor-covenant.org/translations][translations].
[homepage]: https://www.contributor-covenant.org
[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations

4
README.md

@ -19,6 +19,10 @@ SPIP Plugin backport of [PHP Supported Versions](http://php.net/supported-versio
- `<supportedversions|pre_releases>` : list of pre-releases in JSON
- `<supportedversions|stable>` : Gives informations of the last stable version released with `info` parameter (version, date or url)
## Filters
- `|SupportedVersions::getBranchValues` : Array of branch data for a given release string
## Other usage
Calling `/spip.php?page=supported-versions.svg` renders a calendar in svg format.

2
paquet.xml

@ -1,7 +1,7 @@
<paquet
categorie="date"
prefix="supportedversions"
version="0.4.0"
version="0.4.1"
etat="experimental"
compatibilite="[3.2;["
>

Loading…
Cancel
Save