v1.3.4-app-bundle-support-build-4

This build updates the macOS app-bundle install flow so existing app bundles are replaced automatically when an install is needed.

What changed:

• Automatic macOS app installs no longer stop for replace, skip, or abort when the destination .app already exists.
• When an app install is needed, Eget now replaces the existing destination app bundle automatically.
• With --upgrade-only, apps that are already up to date are still skipped individually, while older installed app bundles are replaced without prompting.
• CLI binary install behavior is unchanged.

Related behavior already supported in this fork:

• target_app can be set in config to control automatic macOS app-bundle destinations separately from CLI binary target.
• Automatic macOS app installs still apply the existing precedence order: explicit --to, then target_app, then target, then /Applications.

Example config:

[global]
target = "~/bin"
target_app = "/Applications"

v1.3.4-app-bundle-support-build-3

This build adds two macOS app-install improvements on top of the app-bundle support fork.

• Added target_app config for automatic macOS .app installs.
• Fixed DMG mount-point parsing so automatic app discovery works for DMGs whose hdiutil attach output includes trailing device-only lines.

How to use target_app:

[global]
target = "~/bin"
target_app = "/Applications"

Behavior:

• target continues to control CLI binary installs.
• target_app applies only to automatic macOS app-bundle installs.
• Precedence for automatic macOS app installs is: explicit --to, then target_app, then target, then /Applications.
• Automatic app installs still trigger only when the selected macOS archive resolves to one or more .app bundles; normal CLI-binary behavior is unchanged.

v1.3.4-app-bundle-support-build-2

This build adds target_app configuration support for automatic macOS app installs.

How to use it:

[global]
target = "~/bin"
target_app = "/Applications"

Behavior:

• target continues to control normal CLI binary installs.
• target_app applies only to automatic macOS .app bundle installs.
• For automatic macOS app installs, destination precedence is: explicit --to, then target_app, then target, then /Applications.
• If target_app is set, app bundles no longer inherit the CLI binary destination from target.
• Existing CLI binary behavior is otherwise unchanged.

This release keeps the existing macOS app-bundle auto-install support, multi-app install behavior, quarantine removal, and timestamp-based --upgrade-only logic.

v1.3.4-app-bundle-support

Adds automatic macOS .app bundle installation to /Applications for app-capable assets on Darwin while preserving existing CLI-binary behavior, and now supports --upgrade-only for automatic macOS app installs using source timestamps. GitHub releases use release creation time, direct URLs use Last-Modified when available, local files use source file mtime, and multi-app assets are upgraded per app.