tableau-public 2024.3.0

[GraySinclair]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

[p-linnane]

I've verified that this version of the app is still using the same source when checking for updates, but it hasn't been updated yet. @samford Any concerns with merging this?

[samford]

I've verified that this version of the app is still using the same source when checking for updates, but it hasn't been updated yet. Any concerns with merging this?

If the Public app checks the same XML file, then I suppose we can assume that Desktop and Public versions are strictly aligned. TableauAutoUpdate.xml references TableauDesktop files (not TableauPublic) and both tableau/tableau-public use the same check. [I'll create a separate PR to update the -prep/-public/-reader livecheck blocks to use cask references instead of duplicating the livecheck block (#192118), as tableau can potentially be seen as the parent cask.]

The highest version on the Desktop releases page is 2024.3 ("Released Oct 15, 2024") but 2024.2.4 was released later on Oct 24, 2024. The highest version in the XML file is 2024.2.4, so the file has been updated after the 2024.3 release but it doesn't include it. There's no way to tell if upstream has intentionally omitted 2024.3 (to prevent users from upgrading to it until sometime in the future) or if they just haven't made some technical change to include it in the XML file.

How we handle this mismatch depends on if our aim is to replicate the same behavior as the auto-update logic in the application or if we just want to use the highest released version. If it's the former then we can mark this as a draft and wait for the XML file to include 2024.3.0. If it's the latter, then we would need to update the livecheck block to check the releases page instead.

I put together a livecheck block that checks the releases page (it also requires a strategy block to add .0 to two-part versions), so I can push that here if we go that route.