-
Notifications
You must be signed in to change notification settings - Fork 554
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
Add support for sponsorship packages #26926
Conversation
Mainly to get access to new commercial-shared sponsored tag wording
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 This does not impact any work that we are currently doing as far as I can see
Thank you for this @davidfurey! This really helped out me and @frederickobrien as we needed to test a new version of the CAPI client on #26931, which due to the breaking changes of v20 and v21 would have been much more work if we hadn't been able to rebase from this branch 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Seen on ADMIN-PROD (merged by @davidfurey 12 minutes and 14 seconds ago)
|
Seen on FRONTS-PROD (merged by @davidfurey 13 minutes and 18 seconds ago)
|
Just for information here is the upstream commercial-shared PR guardian/commercial-shared#59 |
What is the value of this and can you measure success?
Allows US advertising team to sell sponsorships with "Advertising partner" and "Exclusive advertising partner" wording. See guardian/tagmanager#508 for more information.
This mainly involves library bumps, but since the CAPI library hasn't been bumped since the recipe atom was deprecated and the recipe element created, there are unfortunately a couple of commits to tidy that up that are unrelated to my main goal. See guardian/content-atom#161