duckduckgo / duckduckgo/Android

[Android Maintenance] Bump native-github-asana-sync to v2.6.0

Open
#9,182 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agentic-maintenance agentic-workflows
Dominant language
Kotlin
Stars
4.8k
Forks
1.4k
Avg merge
2d 17h
Merged PRs (30d)
170

Description

Task/Issue URL: https://app.asana.com/1/137249556945/project/414730916066338/task/1216542927950821
Tech Design URL (if applicable):

Description

New release of the Asana <> GitHub integration action: v2.6.0. Per the release notes, downstream workflows should be pinned to duckduckgo/native-github-asana-sync@v2.6.0.

This PR bumps every reference to duckduckgo/native-github-asana-sync across .github/workflows/ and .github/actions/ to v2.6.0, bringing the whole repo onto a single, consistent version. Previously references were spread across v2.0, v2.3, v2.4, and v2.5.1.

Changes are line-for-line version swaps only (53 insertions / 53 deletions) — no workflow logic was modified:

  • uses: duckduckgo/native-github-asana-sync@… references updated in 22 workflow/action files.
  • The actions/checkout ref: for the native-github-asana-sync repo in privacy-review.yml updated from v2.4 to v2.6.0.
  • pr-review-notifications.yaml was already on v2.6.0 and is left unchanged.

v2.6.0 is a minor release within the v2 major line, so it is backward compatible with the actions these workflows invoke (release notes).

🤖 Android Maintenance Worker

Steps to test this PR

Lint / formatting

  • These are GitHub Actions YAML config changes only — no Kotlin/Java or Gradle module code is touched, so spotlessCheck, lint_check, and module unit tests are not applicable and were not run (no modified modules).
  • All 24 changed YAML files were validated to parse cleanly.
  • Confirmed the v2.6.0 tag/release exists in duckduckgo/native-github-asana-sync.
UI changes
Before After
No UI changes No UI changes

[!NOTE]

🔒 Integrity filter blocked 3 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #9090 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #8860 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #8844 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Android Maintenance Worker ·


[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Workflow Run: View run details and download patch artifact

The patch file is available in the agent artifact in the workflow run linked above.

To create a pull request with the changes:

# Download the artifact from the workflow run
gh run download 29392332234 -n agent -D /tmp/agent-29392332234

# Create a new branch
git checkout -b chore/maintenance/asana-sync-v2.6.0-d2f86578465a9929

# Apply the patch (--3way handles cross-repo patches where files may already exist)
git am --3way /tmp/agent-29392332234/aw-chore-maintenance-asana-sync-v2.6.0.patch

# Push the branch to origin
git push origin chore/maintenance/asana-sync-v2.6.0-d2f86578465a9929

# Create the pull request
gh pr create --title '[Android Maintenance] Bump native-github-asana-sync to v2.6.0' --base develop --head chore/maintenance/asana-sync-v2.6.0-d2f86578465a9929 --repo duckduckgo/Android
Show patch preview (500 of 615 lines)
From 62292acbc298c7d5a2290bf1122134540644fff2 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Wed, 15 Jul 2026 05:50:49 +0000
Subject: [PATCH] Bump native-github-asana-sync to v2.6.0

Update all workflow references of duckduckgo/native-github-asana-sync
to v2.6.0 as requested by the Asana <> Github Integration release.

Task: https://app.asana.com/1/137249556945/project/414730916066338/task/1216542927950821

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .github/actions/assign-release-task/action.yml       |  2 +-
 .../actions/maestro-cloud-asana-reporter/action.yml  |  4 ++--
 .github/workflows/action-agentic-maintenance-pr.yaml |  4 ++--
 .github/workflows/action-issue-opened.yaml           |  2 +-
 .github/workflows/action-pr-merged.yaml              |  2 +-
 .github/workflows/action-pr-opened.yaml              |  6 +++---
 .github/workflows/e2e-duckplayer.yml                 |  2 +-
 .github/workflows/e2e-nightly-full-suite.yml         |  2 +-
 .github/workflows/e2e-nightly-non-blockers-suite.yml |  2 +-
 .github/workflows/e2e-nightly-sync-critical-path.yml |  4 ++--
 .github/workflows/nightly-metro.yml                  |  2 +-
 .github/workflows/nightly-orchestrator.yml           |  4 ++--
 .github/workflows/nightly.yml                        |  4 ++--
 .github/workflows/privacy-review.yml                 |  2 +-
 .github/workflows/privacy.yml                        |  4 ++--
 .github/workflows/ps-review-analysis.yml             |  2 +-
 .github/workflows/release_create_tag.yml             |  8 ++++----
 .github/workflows/release_create_task.yml            |  8 ++++----
 .github/workflows/release_update_release_notes.yml   |  2 +-
 .github/workflows/release_upload_internal.yml        |  2 +-
 .github/workflows/release_upload_play_store.yml      | 12 ++++++------
 .github/workflows/update-content-scope.yml           | 10 +++++-----
 .github/workflows/update-pir-broker-bundle.yml
... (truncated)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search .github/workflows/ and .github/actions/ for every duckduckgo/native-github-asana-sync reference, including the checkout ref in privacy-review.yml, and compare them with the listed files. Validate all changed YAML files and confirm every reference uses v2.6.0 while leaving pr-review-notifications.yaml unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.