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 #5895] [BRE-1194] temporarily enable hourly checks for github release #6133

New Issue
Closed
opened 2025-11-27 00:20:08 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-27 00:20:08 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/bitwarden/android/pull/5895

State: closed
Merged: Yes

This updated was tested during the 10/2/25 clients release

Added dry-run option to publish-store.yml

publish-store.yml will enable github release workflows once release to the ios app store is complete.

publish-github-release.yml is now publish-github-release-bwa.yml and publish-github-release-bwa.yml so that they can be enabled or disabled based on which project was released. They now run hourly when enabled.

The workflow gh-actions/_publish-mobile-github-release.yml disables the workflow that ran it once it completes successfully.

🎟️ Tracking

Original Ticket
Follow up for testing

📔 Objective

Right now the check runs at 3am M-F, so if it fails on a Friday it doesn’t run again until Monday, which causes CI jobs to fail. This happens since they use the existing GH release to determine the version and cannot upload using the same version that’s currently rolling out.

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) 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
**Original Pull Request:** https://github.com/bitwarden/android/pull/5895 **State:** closed **Merged:** Yes --- This updated was tested during the 10/2/25 clients release Added dry-run option to publish-store.yml publish-store.yml will enable github release workflows once release to the ios app store is complete. publish-github-release.yml is now publish-github-release-bwa.yml and publish-github-release-bwa.yml so that they can be enabled or disabled based on which project was released. They now run hourly when enabled. The workflow gh-actions/_publish-mobile-github-release.yml disables the workflow that ran it once it completes successfully. ## 🎟️ Tracking [Original Ticket](https://bitwarden.atlassian.net/browse/BRE-1118) [Follow up for testing](https://bitwarden.atlassian.net/browse/BRE-1194) ## 📔 Objective Right now the check runs at 3am M-F, so if it fails on a Friday it doesn’t run again until Monday, which causes CI jobs to fail. This happens since they use the existing GH release to determine the version and cannot upload using the same version that’s currently rolling out. ## 📸 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 - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) 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
GiteaMirror added the pull-request label 2025-11-27 00:20:08 -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#6133
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?