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

Update CHANGELOG and bump version for release #1319

Closed

Conversation

mathieujobin
Copy link

No description provided.

@mathieujobin mathieujobin mentioned this pull request Nov 8, 2023
@@ -1,5 +1,5 @@
# frozen_string_literal: true

module Prawn
VERSION = '2.4.0'
VERSION = '2.5.0'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand the sentiment but generally this is not done in a PR. I have not decided yet on the version that's going to be released.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right makes sense. I put my reasoning there. #1195 (comment)

### Look for glyph in correct font

Take the font style into account when looking for a glyph and fallback fonts are enabled.

(Dan Allen, [#1147](https://github.com/prawnpdf/prawn/issues/1147))

### Raise an exception on invalid valign value

(Masakinpo)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we have PRs associated with these changes? I might've been cheeky and push to master once ina while but most of the contributions probably had a PR opened first.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the way things was merged, this information is really hard to track. I'm not going to spend the time tracking down this past 3 years

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. Thank you.

@pointlessone
Copy link
Member

@mathieujobin Thank you for your effort but I did it myself in the end.

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

Successfully merging this pull request may close these issues.

2 participants