-
Notifications
You must be signed in to change notification settings - Fork 521
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 manifest-v3.md from Jan to June #3041
Update manifest-v3.md from Jan to June #3041
Conversation
v3 coming June 2024: https://developer.chrome.com/blog/resuming-the-transition-to-mv3
microsoft-edge/extensions-chromium/developer-guide/manifest-v3.md
Outdated
Show resolved
Hide resolved
@JesseHufstetlerNortridge , d/k why bot is re-posting about CLA. I haven't seen that behavior. If needed, I could create a fresh PR with all these commits, and Close Without Merging the present PR. A nice thing about using present PR is that the article will list you as contributor, i think. I might delete some bot posts here ... they went away. I just have the multiple emails. |
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.
Approved PR after pushing commits for a Writer/Editor pass of entire article. Broke out the paragraph (from original PR/commit) to differentiate 2 scenarios.
Learn Build status updates of commit bf93d24: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@JesseHufstetlerNortridge please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
@JesseHufstetlerNortridge - Can you "sign" the Contributor License Agreement, per emails from GitHub and per the above bot post? I believe if you sign CLA so this PR can be merged, you will be listed as a contributor at top of article: |
Learn Build status updates of commit b5d3dbb: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
This PR 3041 is being replaced by PR #3076. |
Updated PR #3076 to remove the date from the sentence. @JesseHufstetlerNortridge |
Rendered article section for review:
v3 is coming June (not Jan) 2024, per:
https://developer.chrome.com/blog/resuming-the-transition-to-mv3#the_phase-out_timeline [except that depends whether using enterprise policies, which is the scenario that the original paragraph specified - m.h.]
Update by m.h.:
AB#48777833