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

Release 2.6.1 #2299

Merged
merged 35 commits into from
Mar 5, 2024
Merged

Release 2.6.1 #2299

merged 35 commits into from
Mar 5, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 5, 2024

Checklist

  1. Check if the version, base, and target branches are as you desire.
  2. Make sure you have woorelease installed and set up.
  3. Go to your local repo clone, and check out this PR to be able to commit any potential adjustments.
    git fetch origin release/2.6.1
    git checkout release/2.6.1
  4. Remove older changelog entries from readme.txt (keep the last two versions, since we will be adding a third during the release), commit changes.
  5. If there are new database migration classes (under src/DB/Migration/), modify their applicable version set in the get_applicable_version class of each migration class to be the same value as the version that is to be released.
    ⚠️ Notice that x.x.x is not a valid version and should be set manually with the new version. So, for example, if we are releasing version 1.12.0 and there is a file Migration20211228T1640692399.php inside src/DB/Migration/, you should open that file and in the method get_applicable_version return 1.12.0.
  6. ❗ If this release has updated composer packages, we should test Composer package conflicts with other plugins.
  7. Simulate the release locally
    woorelease simulate --product_version=2.6.1  --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.6.1
    Note: Select y when prompted: "Would you like to add/delete them in the svn working copy?"
  8. The changelog is correct.
    Check if some entries are missing, need rewording, or need to be deleted. You can edit respective PRs by changing their title, ### Changelog entry section, or assigning the changelog: none label.
    You can also edit the changelog manually in the woorelease release step later.
  9. Automated tests are passing. (E2E tests failed but there is a PR here Grant consent before checking the gtag events #2294
  10. Test the package
    1. Install the /tmp/google-listings-and-ads.zip file on a test site
    2. Confirm it activates without warnings/errors and is showing the right versions
    3. Run a few basic smoke tests

Next steps

  1. Do the final release
    woorelease release --product_version=2.6.1   --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.6.1
    
    When prompted for changelog entries, double-check and apply any changes if needed.
  2. Go to https://github.com/woocommerce/google-listings-and-ads/releases/2.6.1, generate GitHub release notes, and paste them as a comment here.
  3. Merge this PR after the new release is successfully created and the version tags are updated.
  4. Merge trunk to develop (PR), if applicable for this repo.
  5. Update documentation
    • Publish any new required docs
    • Update triggers/rules/actions listing pages
  6. Mark related ideas complete on the feature requests page.

eason9487 and others added 30 commits February 27, 2024 12:05
Release 2.6.0 - Merge `trunk` to `develop`
…analytics-version-2-enabled

Consider `ga_gtag_enabled=yes` for  WCGAI >= 2
Co-authored-by: Tomek Wytrębowicz <[email protected]>
…st-data-plugin

Avoid the test-data plugin occasionally missing in the E2E test environment
…analytics-version-2

Add support for Google Analytics for WooCommerce version 2.0.0
…ndling

Improve WordPress.com account handling
Copy link

codecov bot commented Mar 5, 2024

Codecov Report

Attention: Patch coverage is 22.98851% with 67 lines in your changes are missing coverage. Please review.

Project coverage is 62.1%. Comparing base (ca99261) to head (f07ed32).

❗ Current head f07ed32 differs from pull request most recent head 271f164. Consider uploading reports for the commit 271f164 to get more accurate results

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##             trunk   #2299     +/-   ##
=========================================
- Coverage     62.2%   62.1%   -0.1%     
- Complexity    4190    4205     +15     
=========================================
  Files          748     748             
  Lines        21547   21593     +46     
  Branches       532     532             
=========================================
+ Hits         13406   13418     +12     
- Misses        7690    7724     +34     
  Partials       451     451             
Flag Coverage Δ
js-unit-tests 54.0% <ø> (ø)
php-unit-tests 63.8% <23.0%> (-0.1%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
google-listings-and-ads.php 75.0% <ø> (ø)
src/API/Google/Middleware.php 86.8% <100.0%> (+1.1%) ⬆️
...API/Site/Controllers/Jetpack/AccountController.php 100.0% <100.0%> (ø)
src/Proxies/GoogleGtagJs.php 0.0% <0.0%> (ø)
src/ConnectionTest.php 0.0% <0.0%> (ø)
src/Google/GlobalSiteTag.php 0.0% <0.0%> (ø)

@jorgemd24
Copy link
Contributor

What's Changed

[Add] New Features 🎉

[Update] Updated ✨

[Fix] Fixes 🛠

[Dev] Developer-facing changes 🧑‍💻

Full Changelog: 2.6.0...2.6.1

@jorgemd24 jorgemd24 merged commit c201243 into trunk Mar 5, 2024
@jorgemd24 jorgemd24 deleted the release/2.6.1 branch March 5, 2024 18:58
@jorgemd24 jorgemd24 self-assigned this Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants