Skip to content

Releases: asale-ai/asale

Asale client v0.2.2

Choose a tag to compare

@github-actions github-actions released this 04 Aug 07:50

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed — the build asserts this when the
    Azure credentials are configured, but on a fresh Windows machine also check that
    Get-AuthenticodeSignature reports Valid and that SmartScreen stays quiet
    (a brand-new certificate has no reputation yet and can still warn for a while)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.2.1

Choose a tag to compare

@github-actions github-actions released this 04 Aug 05:48

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed — the build asserts this when the
    Azure credentials are configured, but on a fresh Windows machine also check that
    Get-AuthenticodeSignature reports Valid and that SmartScreen stays quiet
    (a brand-new certificate has no reputation yet and can still warn for a while)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.2.0

Choose a tag to compare

@github-actions github-actions released this 03 Aug 10:51

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed — the build asserts this when the
    Azure credentials are configured, but on a fresh Windows machine also check that
    Get-AuthenticodeSignature reports Valid and that SmartScreen stays quiet
    (a brand-new certificate has no reputation yet and can still warn for a while)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.1.10

Choose a tag to compare

@github-actions github-actions released this 03 Aug 09:49

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed — the build asserts this when the
    Azure credentials are configured, but on a fresh Windows machine also check that
    Get-AuthenticodeSignature reports Valid and that SmartScreen stays quiet
    (a brand-new certificate has no reputation yet and can still warn for a while)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.1.8

Choose a tag to compare

@github-actions github-actions released this 03 Aug 07:18

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed — the build asserts this when the
    Azure credentials are configured, but on a fresh Windows machine also check that
    Get-AuthenticodeSignature reports Valid and that SmartScreen stays quiet
    (a brand-new certificate has no reputation yet and can still warn for a while)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.1.7

Choose a tag to compare

@github-actions github-actions released this 31 Jul 06:16

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed — the build asserts this when the
    Azure credentials are configured, but on a fresh Windows machine also check that
    Get-AuthenticodeSignature reports Valid and that SmartScreen stays quiet
    (a brand-new certificate has no reputation yet and can still warn for a while)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.1.6

Choose a tag to compare

@github-actions github-actions released this 30 Jul 12:29

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed — the build asserts this when the
    Azure credentials are configured, but on a fresh Windows machine also check that
    Get-AuthenticodeSignature reports Valid and that SmartScreen stays quiet
    (a brand-new certificate has no reputation yet and can still warn for a while)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.1.5

Choose a tag to compare

@github-actions github-actions released this 29 Jul 11:32

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed (otherwise SmartScreen warns)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.1.4

Choose a tag to compare

@github-actions github-actions released this 29 Jul 01:55

Installers for all three platforms, built by the release workflow.

Before publishing, confirm:

  • the macOS .dmg is signed and notarized (otherwise other machines report it as damaged)
  • the Windows installer is Authenticode-signed (otherwise SmartScreen warns)
  • every bundle has a matching .sig next to it (required for auto-update)
  • install once and verify login and going on the market, then publish manually

Asale client v0.1.3

Choose a tag to compare

@github-actions github-actions released this 28 Jul 15:10

What's new

All five subscriptions can now be sold. Kimi Code and Grok CLI sign in through RFC 8628 device-code authorization — you confirm a short code in the browser, with no callback port involved, so these two also work from a remote browser session. Claude Code, Codex and Gemini CLI keep the browser-callback flow. Each vendor's metered platform API key can be connected separately.

On the buying side, config switching still covers Claude Code, Codex and Gemini CLI.

Downloads

Platform File
macOS (universal) Asale_0.1.3_universal.dmg
Windows (x64) Asale_0.1.3_x64-setup.exe or Asale_0.1.3_x64_en-US.msi
Linux (x64) Asale_0.1.3_amd64.deb or Asale_0.1.3_amd64.AppImage

The macOS bundle is signed with a Developer ID and notarized by Apple. The Windows installer is not Authenticode-signed yet, so SmartScreen shows an "unknown publisher" warning on first run.

.sig files are updater signatures, not needed for a manual install.