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

Getting a new stable release #60

Closed
dalibor-matura opened this issue Oct 11, 2018 · 2 comments
Closed

Getting a new stable release #60

dalibor-matura opened this issue Oct 11, 2018 · 2 comments

Comments

@dalibor-matura
Copy link

Problem/Motivation

There wasn't a stable release for almost a year and we would really like to use the fix from commit mickaelperrin@698b124, but composer requirements/restrictions are not going to allow us to use master-dev verson of this package.

The commit (master branch) holds a fix #51 for this #49 (comment)

Expected behaviour & Proposed change

Have a new stable release 0.4.5 (or 0.5.0) with all the fixes we could update to.

Obviously it needs to be reviewed first.

Actual behaviour

There a lot of commits in master branch after the last stable version 0.4.4 was released.

It is possible that a good number of people can not use these fixes because composer setup on their project doesn't allow to use unstable version of the package.

@Potherca
Copy link
Member

If @frenck agrees, I would like to add #51, #54, #60 and #62 and tag a new release v0.5.0.

@frenck
Copy link
Contributor

frenck commented Oct 25, 2018

This issue is mainly a request and not an issue. A new release will follow soon, closing this issue, because it isn't an issue.

@frenck frenck closed this as completed Oct 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants