Create a release about forceutf8

[jibriss]

Hello,

I have the same issue, adding a "dev-master" dependency in our project is very stressful :)

I saw a version in the file

@version  1.2

So I guess you can tag it "v1.2".

Anyway, thanks for your good work, this library is very helpful !

[obukhov]

+1

[el-seirh]

+1. Targeting master makes me feel shaky ;). Good lib anyway!

[MaxGfeller]

+1. And please follow the semantic versioning guidelines which make it a lot easier for fellow developers to depend on your library.

[annavanbiemen]

+1

[neitanod]

Thanks for the advice. I will as soon as I can.

[neitanod]

I created this release: https://github.com/neitanod/forceutf8/releases/tag/v1.4
As well as a branch to make fixes to versions v1.*: https://github.com/neitanod/forceutf8/tree/v1

Soon I will release v2.0 wich adds a dependency (iconv) to deal with some Win1252 special chars that v1 can't handle. For now those improvements are on the master branch.

I'm new to Composer. Can anyone give me a hand on how should the json be adapted to the new release? @jibriss, @obukhov, @MaxGfeller, @el-seirh, anyone? :)

Also, does anybody know how the Packagist entry should be updated?

[el-seirh]

I think you don't need to update anything in the json of the project.

To make your package on Packagist getting updated:
"Existing packages without auto-updating (GitHub/BitBucket hook) will be crawled once a day for updates. " (see https://packagist.org/about)

We as users then only have to change our "require" in the composer.json to:

{
    "require": {
        "neitanod/forceutf8": "1.*"
    }
}

Also make sure that you follow the semantic versioning, as @MaxGfeller pointed out (e.g. "v1.0.0").

I hope that's all. Good luck and thanks again for your work ;)

[el-seirh]

As an alternative I think you can also click "Force update" when you login into Packagist directly.

But the best way would of course be to go here and check the section "GitHub Service Hook". This should explain all the details on how to set up the hook on GitHub.

[neitanod]

I know that there's no need to change the json of the project, but I would like to update the README that explains how to include it, showing an example of the json of the user.

About Packagist... I'm not the maintainer of that entry, so I don't exactly know what to do. I am trying to contact Nidelson, the maintainer.

[el-seirh]

So yeah, all you have to change in the README is

{
    "require": {
        "neitanod/forceutf8": "1.*"
    }
}

to make people use your major version 1 (since bigger MAJOR versions wouldn't be backwards compatible according to semantic versioning).

[el-seirh]

About packagist: I guess you will just have to wait for the daily update if you are not the owner since for the auto-update hook on GitHub you require the API token from packagist.