github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 11:44:41 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[PR #3892] [MERGED] Use an aar to define bridge dependency #4501

New Issue
Closed
opened 2025-11-26 23:45:29 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 23:45:29 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/3892
Author: @ahaisting-livefront
Created: 9/10/2024
Status: ✅ Merged
Merged: 9/10/2024
Merged by: @ahaisting-livefront

Base: main ← Head: use-aar

📝 Commits (3)

  • 066b2c4 Use an aar to define bridge dependency
  • b650813 use AAR instead of aar
  • a02f475 use SNAPSHOT on ouput AAR name to avoid confusion

📊 Changes

5 files changed (+21 additions, -2 deletions)

View changed files

📝 app/build.gradle.kts (+2 -2)
➕ app/libs/bridge-0.1.0-SNAPSHOT-release.aar (+0 -0)
➕ app/libs/bridge-0.1.0-release.aar (+0 -0)
📝 bridge/README.md (+9 -0)
📝 bridge/build.gradle.kts (+10 -0)

📄 Description

📔 Objective

The goal here is to fix the failing beta variants on main. When defining bridge as a project dependency, a variant for beta cannot be found. Including an .aar as the dependency resolves this issue.

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
    issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/3892 **Author:** [@ahaisting-livefront](https://github.com/ahaisting-livefront) **Created:** 9/10/2024 **Status:** ✅ Merged **Merged:** 9/10/2024 **Merged by:** [@ahaisting-livefront](https://github.com/ahaisting-livefront) **Base:** `main` ← **Head:** `use-aar` --- ### 📝 Commits (3) - [`066b2c4`](https://github.com/bitwarden/android/commit/066b2c49160333a2ac5f99248ea80f8b4680d761) Use an aar to define bridge dependency - [`b650813`](https://github.com/bitwarden/android/commit/b650813527fc3cd7e866fb1841d0fa24cd0c1145) use AAR instead of aar - [`a02f475`](https://github.com/bitwarden/android/commit/a02f475ab415274a596aef47d42f17c8a78d6b5b) use SNAPSHOT on ouput AAR name to avoid confusion ### 📊 Changes **5 files changed** (+21 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `app/build.gradle.kts` (+2 -2) ➕ `app/libs/bridge-0.1.0-SNAPSHOT-release.aar` (+0 -0) ➕ `app/libs/bridge-0.1.0-release.aar` (+0 -0) 📝 `bridge/README.md` (+9 -0) 📝 `bridge/build.gradle.kts` (+10 -0) </details> ### 📄 Description ## 📔 Objective The goal here is to fix the failing `beta` variants on `main`. When defining `bridge` as a `project` dependency, a variant for `beta` cannot be found. Including an `.aar` as the dependency resolves this issue. ## 📸 Screenshots <!-- Required for any UI changes; delete if not applicable. Use fixed width images for better display. --> ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-26 23:45:29 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#4501
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?