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

dev/mailing#59 Update the version of zetacomponents/mail package to b… #16306

Merged
merged 1 commit into from
Jan 16, 2020

Conversation

seamuslee001
Copy link
Contributor

…e one that potentially will support XAUTH2 for google purposes

Overview

This updates the version of zetacomponents/mail following my PR zetacomponents/Mail#78 being merged in

ping @eileenmcnaughton @demeritcowboy @mfb

@civibot
Copy link

civibot bot commented Jan 16, 2020

(Standard links)

@civibot civibot bot added the master label Jan 16, 2020
@mfb
Copy link
Contributor

mfb commented Jan 16, 2020

@seamuslee001 can you instead update it to v1.9.0 or is a specific git commit still needed?

….9.0 to be one that potentially will support XAUTH2 for google purposes
@@ -48,7 +48,7 @@
"tecnickcom/tcpdf" : "6.2.*",
"totten/ca-config": "~17.05",
"zetacomponents/base": "1.9.*",
"zetacomponents/mail": "dev-master",
"zetacomponents/mail": "1.9.*",
Copy link
Contributor

Choose a reason for hiding this comment

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

Theoretically we could use ^1.9 here? Because later 1.x releases won't break compatibility - unless they do :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

in theory yes but just figured go for the simplest approach right,

Copy link
Member

Choose a reason for hiding this comment

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

If we did that wouldn't we also need to do that for "zetacomponents/base" as well?
I'm happy to merge this PR and have that be a separate discussion.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sure go ahead and merge.

Just thinking that it's best to not be overly restrictive on updates until you know there is (or is likely to be) a problem.

Copy link
Contributor

@mfb mfb Jan 16, 2020

Choose a reason for hiding this comment

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

Looks like zetacomponents/mail:1.9.0 requires zetacomponents/base:~1.8

@seamuslee001
Copy link
Contributor Author

test fail unrelated

@seamuslee001 seamuslee001 merged commit 485fd59 into civicrm:master Jan 16, 2020
@seamuslee001 seamuslee001 deleted the dev_mail_59 branch January 16, 2020 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants