Help you through the complete release of TCF v2.2

[marco-prontera]

Hello @aitnitishshelage, given the need to have the TCF v2.2 and the library that works correctly, I'm writing here what should be done in sequence. Just to help you since this help us to get everything ready and enable us to upgrade our CMPs with the new TCF v2.2

1. Merge of Update to support TCF v2.2 (issue #388). Also fixed an error in the test script #389 (required for IL TCF v2.2 in order for the new parameters to be used as indicated by the IAB)
2. Merge of [#402] Fix tests doesn't run correctly  #403 (required to make sure that the tests all run correctly and to be calm in doing the review)
3. Merge of [#400] Fix GVL must support translations #404 (required because for pt, sr languages we can't use the files that IAB release, see issue related)
4. Merge of [#406] Improve library performance when creating publisher restrictions #407 (required because almost all CMP uses restrictions and without this fix we can't use restrictions for performance reasons)
5. Merge of [#397] TCData useNonStandardTexts #410 (required for TCF v2.2 in order to match all requirements)
6. Merge of [#407] Fix deploy script #409 (required (or maybe optional) to be sure that every release published on NPM is done with yarn postversion, of course develop must be rebased into master)

then release v2.0.0

[marco-prontera]

Hi @iabmayank, I see you are assigned to this, can you help us please?

[marco-prontera]

Hi @iabmayank can you help us please?

[iabmayank]

@marco-prontera please can you open and share the PR and let us know the order in which it's needs to be merged for the release. we will follow the same.

[marco-prontera]

@marco-prontera please can you open and share the PR and let us know the order in which it's needs to be merged for the release. we will follow the same.

Hi @iabmayank, the PRs and the order to merge them is described in this issue, I will also create another PR to update the documentation of this repository. In the mean while you can review and merge the PRs described in this issue and create the release at the end, thanks in advance!

[marco-prontera]

1. Merge of Update to support TCF v2.2 (issue #388). Also fixed an error in the test script #389 (required for IL TCF v2.2 in order for the new parameters to be used as indicated by the IAB)
2. Merge of [#402] Fix tests doesn't run correctly  #403 (required to make sure that the tests all run correctly and to be calm in doing the review)
3. Merge of [#400] Fix GVL must support translations #404 (required because for pt, sr languages we can't use the files that IAB release, see issue related)
4. Merge of [#406] Improve library performance when creating publisher restrictions #407 (required because almost all CMP uses restrictions and without this fix we can't use restrictions for performance reasons)
5. Merge of [#397] TCData useNonStandardTexts #410 (required for TCF v2.2 in order to match all requirements)
6. Merge of [#407] Fix deploy script #409 (required (or maybe optional) to be sure that every release published on NPM is done with yarn postversion, of course develop must be rebased into master)

then release v2.0.0

@iabmayank You can read the list of the PR and merge them in the sequence specified

[marco-prontera]

@iabmayank can you update us, please? Can you let me know when we will see progress?

[lamrowena]

@marco-prontera - this is in progress and will be released soon.

[marco-prontera]

@marco-prontera - this is in progress and will be released soon.

Of course, I opened some PR to finish and get the release ready to let CMPs update their implementation to switch from TCF v2.0 to v2.2.
I also opened an issue and a PR to enable the AMP project fix their implementation to support also the TCF policy version 4.
I also tested the PR (those described in this issue) merged in my own package to implement the CMP and it's successfully validated through the validator extension (https://chrome.google.com/webstore/detail/cmp-validator/ffhhjklgcfabkpholngojpkijlafjooc).
Maybe I'm missing something, maybe there are other reasons I don't know?

[sevriugin]

Merged, thanks cc: @marco-prontera @lamrowena

[mguerra10128]

Is there a estimate of when these merged changed will get released?

[mguerra10128]

just following up here as we are aiming to go live on 2.2 early next week, and require the library changes to be released to complete end to end testing

[sinsimon]

Hello @iabmayank @sevriugin and @lamrowena, we need to plan our CMP TCF 2.2 update as well. Can you give us an estimate on when the merged changed will a release? Thanks

[eldzis]

Hi everyone! We are also waiting for essential tools TCF v2.2 update. Would be great if you could give us any ETA

[marco-prontera]

This issue can be closed. Every changes is published in the new npm package scope @iabtechlabtcf , the code to support the new TCF version is published under 1.5.9 version.
https://www.npmjs.com/search?q=%40iabtechlabtcf