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

Status of Smarty 3.1.36 ? #588

Closed
matks opened this issue Apr 17, 2020 · 8 comments
Closed

Status of Smarty 3.1.36 ? #588

matks opened this issue Apr 17, 2020 · 8 comments

Comments

@matks
Copy link
Contributor

matks commented Apr 17, 2020

Hi guys,

I see there is a release tag 3.1.36 and we can see why it was created. However it has been pending for a few days now and no official release is done ... Is there something blocking ?

Basically I plan to update from 3.1.34 to 3.1.36 when it's ready so I'm wondering if I'll wait for a long time 😄.

If there is no schedule / plan / issue, but you guys just need time, it's OK 👍I'm just wondering whether there are issues we should be aware of

@AnrDaemon
Copy link
Contributor

@matks
Copy link
Contributor Author

matks commented Apr 20, 2020

Indeed packagist now delivers Smarty v3.1.36 but GitHub release is not created (EDIT: not marked as latest)
Capture d’écran 2020-04-20 à 10 01 39

@AnrDaemon
Copy link
Contributor

Open your eyes, the release is right at your screenshot.

@matks
Copy link
Contributor Author

matks commented Apr 20, 2020

My bad, I did use the wrong word. "It's not marked as latest"

And no changelog. Basically it looks like something has yet to be done 😉and I wish to know what so I can decide whether to upgrade or not.

@AnrDaemon
Copy link
Contributor

Because it's a "technical release". Otherwise identical to 3.1.35, with fixed branding.

See https://github.com/smarty-php/smarty/commits/v3.1.36 for details.

@matks
Copy link
Contributor Author

matks commented Apr 23, 2020

Thanks !

@glensc
Copy link
Contributor

glensc commented Aug 20, 2020

Note, the "latest" link also points to latest "latest":

to fix this, maintainer needs to hit "edit" for v3.1.36 and save it at least once

@wisskid
Copy link
Contributor

wisskid commented Aug 22, 2020

Done, thank you, I did not know that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants