Skip to content

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Jul 14, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Updated Node.js version "v22" with a new codename "Jod".
    • Added a new Ubuntu distribution version "v25.04" with the codename "Plucky Puffin" and relevant release information.
    • Introduced a new Debian distribution version "v15" with the codename "Duke".
  • Bug Fixes

    • Modified the start date for Node.js version "v23" to ensure accurate scheduling of releases.

@coderabbitai
Copy link

coderabbitai bot commented Jul 14, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent changes involve updates to version details in JSON files for Node.js, Ubuntu, and Debian distributions. Specifically, the "codename" for Node.js version "v22" has been updated to "Jod," and the "start" date for version "v23" has been changed to "2024-10-16." Additionally, a new entry for Ubuntu version "v25.04" has been added, including its codename "Plucky Puffin," along with details on its creation, release, and end-of-life dates. A new Debian version "v15" has also been introduced with its codename "Duke."

Changes

Files Change Summary
data/node-js-schedule.json Updated "codename" for version "v22" from an empty string to "Jod" and changed "start" date for version "v23" from "2024-10-15" to "2024-10-16."
data/ubuntu-distro-info.json Added new entry for version "v25.04" with attributes: codename "Plucky Puffin," series "plucky," creation date "2024-10-10," release date "2025-04-17," and EOL date "2026-01-15."
data/debian-distro-info.json Added new entry for version "v15" with attributes: codename "Duke," series "duke," and created date "2027-08-01."

Poem

In the meadow where updates play,
New names and dates hop into the fray.
"Jod" for Node, and Puffin so bright,
Versions are dancing, what a delight! 🐰🌼
With every change, the future's in sight,
A joyful leap into tech's warm light!


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot force-pushed the chore/update-static-data branch from 15facf8 to 21f894f Compare July 21, 2024 01:01
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 21f894f to 54bbdbe Compare July 28, 2024 01:01
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 54bbdbe to a8edd52 Compare August 4, 2024 01:02
@github-actions github-actions bot force-pushed the chore/update-static-data branch from a8edd52 to 98c7069 Compare August 11, 2024 01:03
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2ea35f3 and 98c70692f1d164e73239aa468c60ca22e7c093ba.

Files selected for processing (1)
  • data/azure-pipelines-tasks.json (97 hunks)
Additional comments not posted (90)
data/azure-pipelines-tasks.json (90)

3-6: LGTM: Version updates for androidsigning.

The version entries "2.244.1" and "2.244.0" are correctly formatted and consistent with existing entries.


291-301: LGTM: Version updates for azureappservicemanage.

The version entries "0.243.5", "0.243.3", "0.243.1", "0.243.4", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


376-385: LGTM: Version updates for azureappservicesettings.

The version entries "1.243.5", "1.243.3", "1.243.1", "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


427-427: LGTM: Version update for azurecli.

The version entry "1.243.1" is correctly formatted and consistent with existing entries.


436-443: LGTM: Version updates for azurecli and azurefilecopy.

The version entries "1.243.0" for azurecli and "2.244.1" for azurefilecopy are correctly formatted and consistent with existing entries.


458-458: LGTM: Version update for azurefilecopy.

The version entry "2.244.0" is correctly formatted and consistent with existing entries.


547-551: LGTM: Version updates for azurecontainerapps.

The version entries "0.244.1" and "0.244.0" are correctly formatted and consistent with existing entries.


575-579: LGTM: Version updates for azurefilecopy.

The version entries "2.244.1", "2.243.7", "2.243.5", "2.243.3", and "2.243.1" are correctly formatted and consistent with existing entries.


611-615: LGTM: Version updates for azurefilecopy.

The version entries "2.244.0", "2.243.6", "2.243.4", "2.243.2", and "2.243.0" are correctly formatted and consistent with existing entries.


651-655: LGTM: Version updates for maven.

The version entries "3.244.1", "3.243.7", "3.243.5", "3.243.3", and "3.243.1" are correctly formatted and consistent with existing entries.


687-691: LGTM: Version updates for maven.

The version entries "3.244.0", "3.243.6", "3.243.4", "3.243.2", and "3.243.0" are correctly formatted and consistent with existing entries.


727-729: LGTM: Version updates for maven.

The version entries "4.243.5", "4.243.3", and "4.243.1" are correctly formatted and consistent with existing entries.


763-765: LGTM: Version updates for maven.

The version entries "4.243.4", "4.243.2", and "4.243.0" are correctly formatted and consistent with existing entries.


796-798: LGTM: Version updates for maven.

The version entries "5.243.5", "5.243.3", and "5.243.1" are correctly formatted and consistent with existing entries.


835-837: LGTM: Version updates for maven.

The version entries "5.243.4", "5.243.2", and "5.243.0" are correctly formatted and consistent with existing entries.


871-872: LGTM: Version updates for maven.

The version entries "6.243.3" and "6.243.1" are correctly formatted and consistent with existing entries.


905-906: LGTM: Version updates for maven.

The version entries "6.243.2" and "6.243.0" are correctly formatted and consistent with existing entries.


938-938: LGTM: Version update for azurefunctionapp.

The version entry "1.244.0" is correctly formatted and consistent with existing entries.


1312-1326: LGTM: Version updates for azurefunctionappcontainer.

The version entries "1.244.1", "1.243.5", "1.243.3", "1.243.1", "1.244.0", "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


1392-1433: LGTM: Version updates for azurefunctionapp.

The version entries "1.244.1", "1.243.5", "1.243.3", "1.243.1", "1.244.0", "1.243.4", "1.243.2", "1.243.0", "2.244.3", "2.244.1", "2.243.9", "2.243.7", "2.243.5", "2.243.3", "2.243.1", "2.244.2", and "2.244.0" are correctly formatted and consistent with existing entries.


1542-1562: LGTM: Version updates for azurefunctiononkubernetes.

The version entries "0.244.3", "0.244.1", "0.244.2", "0.244.0", "1.243.5", "1.243.3", "1.243.1", "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


1615-1624: LGTM: Version updates for azureiotedge.

The version entries "2.243.5", "2.243.3", "2.243.1", "2.243.4", "2.243.2", and "2.243.0" are correctly formatted and consistent with existing entries.


1669-1671: LGTM: Version updates for azurekeyvault.

The version entries "1.244.1", "1.243.3", and "1.243.1" are correctly formatted and consistent with existing entries.


1681-1692: LGTM: Version updates for azurekeyvault.

The version entries "1.244.0", "1.243.2", "1.243.0", "2.243.3", and "2.243.1" are correctly formatted and consistent with existing entries.


1701-1702: LGTM: Version updates for azurekeyvault.

The version entries "2.243.2" and "2.243.0" are correctly formatted and consistent with existing entries.


1798-1812: LGTM: Version updates for azuremysqldeployment.

The version entries "1.244.1", "1.243.5", "1.243.3", "1.243.1", "1.244.0", "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


1905-1909: LGTM: Version updates for azurenlbmanagement.

The version entries "1.244.1" and "1.244.0" are correctly formatted and consistent with existing entries.


1931-1933: LGTM: Version updates for azurepowershell.

The version entries "4.243.5", "4.243.3", and "4.243.1" are correctly formatted and consistent with existing entries.


1960-1962: LGTM: Version updates for azurepowershell.

The version entries "4.243.4", "4.243.2", and "4.243.0" are correctly formatted and consistent with existing entries.


1988-1991: LGTM: Version updates for azurepowershell.

The version entries "5.243.7", "5.243.5", "5.243.3", and "5.243.1" are correctly formatted and consistent with existing entries.


2024-2027: LGTM: Version updates for azurepowershell.

The version entries "5.243.6", "5.243.4", "5.243.2", and "5.243.0" are correctly formatted and consistent with existing entries.


2057-2057: LGTM: Version update for azurepowershell.

The version entry "2.244.0" is correctly formatted and consistent with existing entries.


2120-2120: LGTM: Version update for azurepowershell.

The version entry "3.244.0" is correctly formatted and consistent with existing entries.


2350-2357: LGTM: Version updates for azureresourcegroupdeployment.

The version entries "2.243.3", "2.243.1", "2.243.2", and "2.243.0" are correctly formatted and consistent with existing entries.


2455-2464: LGTM: Version updates for azureresourcemanagertemplatedeployment.

The version entries "3.243.1", "3.242.1", "3.243.0", and "3.242.0" are correctly formatted and consistent with existing entries.


2543-2560: LGTM: Version updates for azurermwebappdeployment.

The version entries "3.244.1", "3.243.7", "3.243.5", "3.243.3", "3.243.1", "3.244.0", "3.243.6", "3.243.4", "3.243.2", and "3.243.0" are correctly formatted and consistent with existing entries.


2570-2586: LGTM: Version updates for azurermwebappdeployment.

The version entries "4.243.7", "4.243.5", "4.243.3", "4.243.1", "4.243.6", "4.243.4", "4.243.2", and "4.243.0" are correctly formatted and consistent with existing entries.


2806-2808: LGTM: Version updates for azurespringcloud.

The version entries "0.243.7", "0.243.3", and "0.243.1" are correctly formatted and consistent with existing entries.


2818-2820: LGTM: Version updates for azurespringcloud.

The version entries "0.243.6", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


2861-2861: LGTM: Version update for azurestaticwebapp.

The version entry "0.243.1" is correctly formatted and consistent with existing entries.


2886-2886: LGTM: Version update for azuretestplan.

The version entry "0.243.1" is correctly formatted and consistent with existing entries.


2906-2906: LGTM: Version update for azuretestplan.

The version entry "0.243.0" is correctly formatted and consistent with existing entries.


2926-2937: LGTM: Version updates for azurevmssdeployment.

The version entries "0.243.5", "0.243.3", "0.243.1", "0.243.4", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


3011-3021: LGTM: Version updates for azurewebappcontainer.

The version entries "1.244.1", "1.243.3", "1.243.1", "1.244.0", and "1.243.2" are correctly formatted and consistent with existing entries.


3092-3107: LGTM: Version updates for azurewebapp.

The version entries "1.244.1", "1.243.5", "1.243.3", "1.243.1", "1.244.0", "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


3253-3259: LGTM: Version updates for cargoauthenticate.

The version entries "0.243.5" and "0.243.0" are correctly formatted and consistent with existing entries.


3300-3305: LGTM: Version updates for cmdline.

The version entries "2.243.1" and "2.243.0" are correctly formatted and consistent with existing entries.


3446-3455: LGTM: Version updates for containerbuild.

The version entries "0.243.3", "0.243.1", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


3496-3504: LGTM: Version updates for containerstructuretest.

The version entries "0.243.3", "0.243.1", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


3538-3544: LGTM: Version updates for copyfilesoverssh.

The version entries "0.243.1" and "0.243.0" are correctly formatted and consistent with existing entries.


Line range hint 3630-3645:
LGTM: Version updates for dockercompose.

The version entries "0.243.3", "0.243.1", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


3644-3645: LGTM: Version updates for dockercompose.

The version entries "0.243.2" and "0.243.0" are correctly formatted and consistent with existing entries.


3714-3715: LGTM: Version updates for dockercompose.

The version entries "1.243.1" and "1.243.0" are correctly formatted and consistent with existing entries.


3744-3770: LGTM: Version updates for docker.

The version entries "0.244.1", "0.244.0", "1.243.1", "1.243.0", "2.243.1", and "2.243.0" are correctly formatted and consistent with existing entries.


4064-4068: LGTM: Version updates for dotnetcoreinstaller.

The version entries "0.244.1" and "0.244.0" are correctly formatted and consistent with existing entries.


4522-4526: LGTM: Version updates for duffleinstaller.

The version entries "0.244.1" and "0.244.0" are correctly formatted and consistent with existing entries.


4595-4616: LGTM: Version updates for filetransform.

The version entries "1.244.3", "1.244.1", "1.244.2", "1.244.0", "2.244.1", and "2.244.0" are correctly formatted and consistent with existing entries.


4672-4675: LGTM: Version updates for ftpupload.

The version entries "1.244.1" and "1.244.0" are correctly formatted and consistent with existing entries.


4753-4757: LGTM: Version updates for githubrelease.

The version entries "0.244.1" and "0.244.0" are correctly formatted and consistent with existing entries.


4871-4875: LGTM: Version updates for gradle.

The version entries "2.244.1" and "2.244.0" are correctly formatted and consistent with existing entries.


5009-5021: LGTM: Version updates for helmdeploy.

The version entries "0.243.11", "0.243.9", "0.243.3", "0.243.1", "0.243.10", "0.243.8", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


5030-5039: LGTM: Version updates for helmdeploy.

The version entries "1.243.11", "1.243.9", "1.243.3", "1.243.1", "1.243.10", "1.243.8", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


5171-5175: LGTM: Version updates for helminstaller.

The version entries "0.244.1" and "0.244.0" are correctly formatted and consistent with existing entries.


5259-5265: LGTM: Version updates for iiswebappdeploymentonmachinegroup.

The version entries "0.243.1" and "0.243.0" are correctly formatted and consistent with existing entries.


5456-5457: LGTM: Version updates for javatoolinstaller.

The version entries "0.243.3" and "0.243.1" are correctly formatted and consistent with existing entries.


5467-5468: LGTM: Version updates for javatoolinstaller.

The version entries "0.243.2" and "0.243.0" are correctly formatted and consistent with existing entries.


5552-5563: LGTM: Version updates for jenkinsdownloadartifacts.

The version entries "1.243.5", "1.243.3", "1.243.1", "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


5699-5708: LGTM: Version updates for kubelogininstaller.

The version entries "0.243.5", "0.243.3", "0.243.1", "0.243.4", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


5717-5732: LGTM: Version updates for kubernetesmanifest.

The version entries "0.244.1", "0.244.0", "1.243.3", "1.243.1", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


5852-5875: LGTM: Version updates for kubernetes.

The version entries "0.244.1", "0.243.3", "0.243.1", "0.244.0", "0.243.2", "0.243.0", "1.243.5", "1.243.3", "1.243.1", "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


6091-6098: LGTM: Version updates for mavenauthenticate.

The version entries "0.243.3", "0.243.1", "0.243.2", and "0.243.0" are correctly formatted and consistent with existing entries.


6127-6153: LGTM: Version updates for maven.

The version entries "3.244.1", "3.243.1", "3.244.0", "3.243.0", "4.243.1", "4.243.0", "2.244.0", and "2.243.0" are correctly formatted and consistent with existing entries.


6397-6406: LGTM: Version updates for mysqldeploymentonmachinegroup.

The version entries "1.244.3", "1.244.1", "1.244.2", and "1.244.0" are correctly formatted and consistent with existing entries.


6522-6530: LGTM: Version updates for npmauthenticate.

The version entries "0.243.1" and "0.243.0" are correctly formatted and consistent with existing entries.


6603-6614: LGTM: Version updates for npmauthenticate.

The version entries "1.244.1", "1.243.1", "1.244.0", and "1.243.0" are correctly formatted and consistent with existing entries.


6724-6728: LGTM: Version updates for nugetauthenticate.

The version entries "1.244.1" and "1.244.0" are correctly formatted and consistent with existing entries.


7222-7240: LGTM: Version updates for packerbuild.

The version entries "0.244.1", "0.243.3", "0.243.1", "0.244.0", "0.243.2", "0.243.0", "1.243.5", "1.243.3", and "1.243.1" are correctly formatted and consistent with existing entries.


7249-7251: LGTM: Version updates for packerbuild.

The version entries "1.243.4", "1.243.2", and "1.243.0" are correctly formatted and consistent with existing entries.


7351-7356: LGTM: Version updates for powershellontargetmachines.

The version entries "1.243.29", "1.243.28", and "1.243.0" are correctly formatted and consistent with existing entries.


7536-7557: LGTM: Version updates for publishcodecoverageresults.

The version entries "1.244.1", "1.243.1", "1.244.0", "1.243.0", "2.242.1", and "2.242.0" are correctly formatted and consistent with existing entries.


7640-7645: LGTM: Version updates for publishsymbols.

The version entries "2.243.1" and "2.243.0" are correctly formatted and consistent with existing entries.


7914-7928: LGTM: Version updates for twineauthenticate.

The version entries "0.244.1", "0.244.0", "1.244.1", and "1.244.0" are correctly formatted and consistent with existing entries.


8010-8010: LGTM: Version update for universalpackages.

The version entry "0.243.1" is correctly formatted and consistent with existing entries.


8020-8020: LGTM: Version update for universalpackages.

The version entry "0.243.0" is correctly formatted and consistent with existing entries.


8105-8113: LGTM: Version updates for usedotnet.

The version entries "2.243.1" and "2.243.0" are correctly formatted and consistent with existing entries.


8379-8379: LGTM: Version update for usedotnet.

The version entry "1.244.0" is correctly formatted and consistent with existing entries.


8543-8547: LGTM: Version updates for xamarinandroid.

The version entries "1.244.1" and "1.244.0" are correctly formatted and consistent with existing entries.


8593-8596: LGTM: Version updates for xamarinios.

The version entries "2.244.1" and "2.244.0" are correctly formatted and consistent with existing entries.


8679-8680: LGTM: Version updates for automatedanalysis and azureappconfigurationsnapshot.

The version entries "0.244.0" for automatedanalysis and "1.244.0" for azureappconfigurationsnapshot are correctly formatted and consistent with existing entries.


8744-8744: LGTM: Version update for azurecloudpowershelldeployment.

The version entry "2.244.0" is correctly formatted and consistent with existing entries.

@github-actions github-actions bot force-pushed the chore/update-static-data branch from 98c7069 to f7d374b Compare August 18, 2024 01:02
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 98c70692f1d164e73239aa468c60ca22e7c093ba and f7d374b6cc712742df39a1ff52ae398d60dd50ed.

Files selected for processing (1)
  • data/azure-pipelines-tasks.json (100 hunks)
Files skipped from review as they are similar to previous changes (1)
  • data/azure-pipelines-tasks.json

@github-actions github-actions bot force-pushed the chore/update-static-data branch from f7d374b to 0234ad0 Compare August 25, 2024 01:03
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f7d374b6cc712742df39a1ff52ae398d60dd50ed and 0234ad04c1131b56300d0b39fa6cf5a4d5a5a252.

Files selected for processing (1)
  • data/azure-pipelines-tasks.json (126 hunks)
Files skipped from review as they are similar to previous changes (1)
  • data/azure-pipelines-tasks.json

@github-actions github-actions bot force-pushed the chore/update-static-data branch from 0234ad0 to 585a456 Compare September 1, 2024 01:10
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0234ad04c1131b56300d0b39fa6cf5a4d5a5a252 and 585a456716d6301b30e8849e0974ce964e32621d.

Files selected for processing (1)
  • data/azure-pipelines-tasks.json (143 hunks)
Additional comments not posted (1)
data/azure-pipelines-tasks.json (1)

Line range hint 1-8911: Overall assessment: Changes look good, no issues found.

The changes in this file involve adding new version strings to the arrays for various Azure Pipelines tasks. This appears to be a routine update to make new versions of the tasks available.

Some key observations:

  • The changes are purely additive, no versions were removed or modified.
  • The new versions follow the existing versioning pattern for each task.
  • Adding new versions should not break existing pipelines that reference older versions.
  • The new versions likely include bug fixes, performance improvements, and possibly new features.

Overall, the changes look good and are safe to merge. The new task versions will be available for users to reference in their pipelines once this is deployed.

@github-actions github-actions bot force-pushed the chore/update-static-data branch from 585a456 to 7074fcf Compare September 8, 2024 01:06
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from f40c3f1 to ff52b6a Compare September 22, 2024 01:08
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 8e1eaf4 to f9fd133 Compare October 6, 2024 01:08
@github-actions github-actions bot force-pushed the chore/update-static-data branch from f9fd133 to 958b8d6 Compare October 13, 2024 01:09
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 7a2495a to ecd7e13 Compare October 27, 2024 01:10
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 543e8f7 to b41afd3 Compare November 10, 2024 01:08
@github-actions github-actions bot force-pushed the chore/update-static-data branch from b41afd3 to 28be8c3 Compare November 17, 2024 01:12
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 28be8c3 to fc44193 Compare November 24, 2024 01:13
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 973db12 to 4573cd3 Compare December 8, 2024 01:16
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 24d6378 to 15f2c07 Compare December 22, 2024 01:10
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from bac664c to 3f503f6 Compare January 5, 2025 01:10
@github-actions github-actions bot force-pushed the chore/update-static-data branch from db4007e to 5ae9e8b Compare April 27, 2025 01:15
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from a1ebe9c to 0e2b485 Compare May 11, 2025 01:17
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 0e2b485 to 3ea60b2 Compare May 18, 2025 01:18
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 3ea60b2 to 5435274 Compare May 25, 2025 01:19
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 428edb1 to 8a5f0d2 Compare June 8, 2025 01:23
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 4715be7 to c62914e Compare June 22, 2025 01:22
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 1b562e6 to 845d137 Compare July 6, 2025 01:23
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 845d137 to 806b0f8 Compare July 13, 2025 01:25
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 806b0f8 to 0f7bf5f Compare July 20, 2025 01:27
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 0f7bf5f to fbe1312 Compare July 27, 2025 01:27
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 1b813fa to 81b7dc2 Compare August 10, 2025 01:26
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from cf446c4 to d1b3b0c Compare August 24, 2025 01:19
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 3dfd9c9 to 4d54676 Compare September 7, 2025 01:13
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 4d54676 to c0914ad Compare September 14, 2025 01:12
@github-actions github-actions bot force-pushed the chore/update-static-data branch from c0914ad to 52ad53b Compare September 21, 2025 01:14
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from 69bb4df to 506ed09 Compare October 5, 2025 01:14
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 506ed09 to ff3d16b Compare October 12, 2025 01:11
@github-actions github-actions bot force-pushed the chore/update-static-data branch from ff3d16b to a80f951 Compare October 19, 2025 01:17
@github-actions github-actions bot force-pushed the chore/update-static-data branch 2 times, most recently from cf93af6 to 5fd2955 Compare November 9, 2025 01:16
@github-actions github-actions bot force-pushed the chore/update-static-data branch from 5fd2955 to febcf7c Compare November 16, 2025 01:18
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.

2 participants