Doctrine\ORM\Version::VERSION not up to date #5389

Closed
opened 2026-01-22 15:06:09 +01:00 by admin · 4 comments
Owner

Originally created by @PetrHeinz on GitHub (Jan 20, 2017).

Originally assigned to: @Majkl578 on GitHub.

I have noticed that constant Doctrine\ORM\Version::VERSION is not up to date in v2.5.5 and v2.5.6

See:
https://github.com/doctrine/doctrine2/blob/v2.5.4/lib/Doctrine/ORM/Version.php - correct 2.5.4
https://github.com/doctrine/doctrine2/blob/v2.5.5/lib/Doctrine/ORM/Version.php - incorrect 2.5.5-DEV
https://github.com/doctrine/doctrine2/blob/v2.5.6/lib/Doctrine/ORM/Version.php - incorrect 2.5.5-DEV

Originally created by @PetrHeinz on GitHub (Jan 20, 2017). Originally assigned to: @Majkl578 on GitHub. I have noticed that constant Doctrine\ORM\Version::VERSION is not up to date in v2.5.5 and v2.5.6 See: https://github.com/doctrine/doctrine2/blob/v2.5.4/lib/Doctrine/ORM/Version.php - correct 2.5.4 https://github.com/doctrine/doctrine2/blob/v2.5.5/lib/Doctrine/ORM/Version.php - incorrect 2.5.5-DEV https://github.com/doctrine/doctrine2/blob/v2.5.6/lib/Doctrine/ORM/Version.php - incorrect 2.5.5-DEV
admin added the Bug label 2026-01-22 15:06:09 +01:00
admin closed this issue 2026-01-22 15:06:09 +01:00
Author
Owner

@Ocramius commented on GitHub (Jan 20, 2017):

Urgh, I hate that silly version thing. I never remember to update it :-\

@Ocramius commented on GitHub (Jan 20, 2017): Urgh, I hate that silly version thing. I never remember to update it :-\
Author
Owner

@PetrHeinz commented on GitHub (Jan 20, 2017):

I would recommend automation of releasing new versions (for commiting two changes of Version.php and creating a tag) - that would solve it in the future.

@PetrHeinz commented on GitHub (Jan 20, 2017): I would recommend automation of releasing new versions (for commiting two changes of Version.php and creating a tag) - that would solve it in the future.
Author
Owner

@Ocramius commented on GitHub (Jan 20, 2017):

We have that, I just didn't use it because of the huge amount of
repositories I work with, so I forget which ones have automation, and which
don't.

On 20 Jan 2017 6:27 p.m., "Petr Heinz" notifications@github.com wrote:

I would recommend automation of releasing new versions (for commiting two
changes of Version.php and creating a tag) - that would solve it in the
future.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/issues/6246#issuecomment-274129556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakEK0XU6G0mE5Q7L71kzuRh8p9oT3ks5rUO51gaJpZM4LpRyA
.

@Ocramius commented on GitHub (Jan 20, 2017): We have that, I just didn't use it because of the huge amount of repositories I work with, so I forget which ones have automation, and which don't. On 20 Jan 2017 6:27 p.m., "Petr Heinz" <notifications@github.com> wrote: > I would recommend automation of releasing new versions (for commiting two > changes of Version.php and creating a tag) - that would solve it in the > future. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/doctrine/doctrine2/issues/6246#issuecomment-274129556>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAJakEK0XU6G0mE5Q7L71kzuRh8p9oT3ks5rUO51gaJpZM4LpRyA> > . >
Author
Owner

@Majkl578 commented on GitHub (Dec 20, 2017):

Closing this, as of Doctrine 3.0 there won't be any Version class needing manual updates.

@Majkl578 commented on GitHub (Dec 20, 2017): Closing this, as of Doctrine 3.0 there won't be any Version class needing manual updates.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#5389