Issuing releases for minimum Composer stability

[janhartigan]

Right now this library doesn't issue any releases (aka tags) which makes it difficult to target the latest version in Composer. There's a simple solution to this: tag releases in git and (optionally) issue releases on GitHub.

I'll briefly explain semantic versioning and how I use it in Laravel Administrator.

Basic idea for releasing new versions:

• A.B.C, where A is a major potentially compatibility-breaking version release; B is a feature/bugfix release; C is purely a bugfix release
• When you're ready to release a new version, tag the current commit with an annotated tag in this form: v1.0.0. (git tag -a v1.0.0 -m "Version 1.0.0". Then push that tag to GitHub (git push --tags)
• Optional, but nice: once you've pushed the tag, you will be able to look in the releases section and create a new release based on that tag. The release should point to that specific tag and should be titled Version 1.0.0.

This not only helps you better-control the stable release version, but it also helps people target older versions of the library in case they need to for whatever reason.

Edit: this may also help with keeping the packagist entry up to date. It sees a last update from April.

[janhartigan]

Any update on this?

[beporter]

SemVer is pretty important for any package published on Packagist.

It's not safe for consumers of your package to target dev-master since running composer update could cause any breaking changes that might be in your library to get pulled into my project. Even a single, minimal 0.0.1 or 1.0.0 release would let us control how and when we incorporate improvements to your package into our own projects in the future. Please consider publishing at least one semver tag for us to target.