Skip to content

feat(flatpaks): add#64

Merged
castrojo merged 1 commit intoprojectbluefin:mainfrom
castrojo:prep/monkey-bubble
Mar 27, 2026
Merged

feat(flatpaks): add#64
castrojo merged 1 commit intoprojectbluefin:mainfrom
castrojo:prep/monkey-bubble

Conversation

@castrojo
Copy link
Contributor

Add monkey-bubble packaging in testhub with app-specific metadata and CI-ready config.

Assisted-by: Claude Sonnet 4.6 via GitHub Copilot

Package checklist

  • just validate <app> passes (schema + appstreamcli + flatpak-builder-lint)
  • just loop <app> passes (full local build + local registry push)
  • Icon present at 128×128 minimum (/app/share/icons/hicolor/128x128/apps/<app-id>.png)
  • x-version (manifest.yaml) or version (release.yaml) field set to upstream version
  • Source URL is immutable — no rolling tip, latest, or branch archive URLs
  • sha256 matches downloaded artifact
  • finish-args reviewed — each permission justified; non-obvious ones have inline comments
  • MetaInfo XML present and passes appstreamcli validate --no-net
  • Proprietary app: first <p> in description contains disclaimer

Add monkey-bubble packaging in testhub with app-specific metadata and CI-ready config.

Assisted-by: Claude Sonnet 4.6 via GitHub Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Mar 24, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates the 'Monkey Bubble' game into the Flatpak ecosystem by adding its packaging configuration. The changes ensure the application is ready for CI processes and includes all necessary metadata for proper distribution and identification within the testhub.

Highlights

  • New Flatpak Package: Added the monkey-bubble application as a new Flatpak package within the testhub environment.
  • Configuration: Included app-specific metadata and CI-ready configuration for the monkey-bubble Flatpak.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@dosubot dosubot bot added the enhancement New feature or request label Mar 24, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a new flatpak package for 'monkey-bubble'. The configuration is well-structured, but I have a suggestion regarding the source URL. To align with the repository's automated update workflows, the URL should point to the 'latest' artifact rather than a specific version. This ensures that the automated process for updating packages can function correctly.

version: 0.5.33
# arches: upstream generic package provides a single bundle; no aarch64 bundle proven
arches: [x86_64]
url: https://gitlab.com/api/v4/projects/80424238/packages/generic/monkey-bubble/0.5.33/monkey-bubble.flatpak
Copy link
Contributor

Choose a reason for hiding this comment

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

high

To enable automatic updates, the source URL should point to the 'latest' version of the package. Using a version-specific URL will prevent the automated update workflow from fetching new versions.

url: https://gitlab.com/api/v4/projects/80424238/packages/generic/monkey-bubble/latest/monkey-bubble.flatpak
References
  1. For nightly builds with an automated update workflow that pins artifacts via a hash, use a 'latest' URL to enable automatic updates. A permanent, version-specific URL would break this process.

@castrojo castrojo added this pull request to the merge queue Mar 27, 2026
Merged via the queue into projectbluefin:main with commit 70e67b5 Mar 27, 2026
7 checks passed
@castrojo castrojo deleted the prep/monkey-bubble branch March 27, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant