fix: parse the latest deno release in installation script outputs as a tagged version

[haidargit]

Summary

Hi,
This PR improves the console output in the Deno installation part by adjusting the version check logic to handle string values (e.g., v2.3.1). Replaced numeric comparison with a neutral string check. Thanks.

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[salesforce-cla]

Thanks for the contribution! Before we can merge this, we need @haidargit to sign the Salesforce Inc. Contributor License Agreement.

[zimeg]

Hey @haidargit! 👋 Thanks so much for catching this and sending in a fix 🤖 ✨

Before we start review, could you sign the CLA linked from @salesforce-cla? We might have to poke the bot once this is done 😉

[haidargit]

Hi @zimeg 👋, Thanks for the reviews.

Sure. I just signed the CLA agreement, but it only shows the message:
You already signed the CLA on 2025-05-14

[zimeg]

@haidargit Super appreciative of this change! Thanks again for sharing a fix to both the production and development scripts 🙏

I just confirmed this prints both the correct and missing versions as expected:

🔍 Searching for the latest released Deno version... Found: v2.3.1

🔍 Searching for the latest released Deno version... Found: Unknown

For reference of other reviewers, changing the api.github.com URL is sometimes enough to get an unexpected response 👾

More changes to this script might soon follow, but for now this makes for a much better experience. Let's go ahead and merge this for the next release! 🚢 💨

[zimeg]

📝 But before we merge, I forget that semantic versions don't include the v prefix! Oops!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.17%. Comparing base (6ffb164) to head (1678049).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #91   +/-   ##
=======================================
  Coverage   63.17%   63.17%           
=======================================
  Files         210      210           
  Lines       22186    22186           
=======================================
  Hits        14017    14017           
  Misses       7082     7082           
  Partials     1087     1087           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[zimeg]

📝 I took a note that the delete pre-release when a branch is deleted job was stuck in a failed state after reopening this PR for CLA reasons.

I'm wondering if we can make this check pass somehow, but for now that ought not be a blocker!

[haidargit]

appreciate, @zimeg and other team! Thanks ✨

[mwbrooks]

Thanks a lot for the fix @haidargit 🙇🏻 Really appreciate your attention to detail in both the code (both scripts), PR title (convention commits), and PR description (screenshot) 👌🏻 👏🏻

[mwbrooks]

@haidargit Today we prepared Release v3.2.0.

Next week our QA team will review it and then we'll set it as the latest release for the install scripts & slack upgrade command. This should happen next Thursday, May 22nd.

Your install script changes are already live for both the dev build and production build 🎉 You can try them out below:

Latest Release Candidate (Dev Build):

$ curl -fsSL https://downloads.slack-edge.com/slack-cli/install-dev.sh | bash -s slack-dev

$ slack-dev --version
Using slack-dev v3.2.0

Latest Stable Release:

$ curl -fsSL https://downloads.slack-edge.com/slack-cli/install.sh | bash

$ slack --version
Using slack v3.1.0

Thanks again for the contribution 🙇🏻 At the bottom of Release v3.2.0 you're also listed as a first-time contributor 😄

[haidargit]

Thanks for merging this @mwbrooks, @zimeg, and slack-api team ⭐
Really cool to be part of contributor. Appreciate it! 🙇🏻