Skip to content

docs(scalingo-26): first page#3759

Draft
EtienneM wants to merge 3 commits into
feat/scalingo-22-eol-noticefrom
feat/STORY-3788/scalingo-26
Draft

docs(scalingo-26): first page#3759
EtienneM wants to merge 3 commits into
feat/scalingo-22-eol-noticefrom
feat/STORY-3788/scalingo-26

Conversation

@EtienneM
Copy link
Copy Markdown
Member

@EtienneM EtienneM commented May 26, 2026

Warning

Requires #3756 to be merged before merging this one

I keep this PR as a draft as I don't want to merge it before the stack is actually released. But it's already reviewable.

@EtienneM EtienneM self-assigned this May 26, 2026
@notion-workspace
Copy link
Copy Markdown

@EtienneM EtienneM changed the base branch from master to feat/scalingo-22-eol-notice May 26, 2026 07:31
| **`1.24`** | up to `1.24.13` | up to `1.24.13` | up to `1.24.13` |

The default Go version on all stacks is the latest `go1.24` version.
The default Go version on all stacks is the latest `go1.25` version.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I noticed this while working on this page, but it's unrelated to my work.

@EtienneM EtienneM requested review from a team, Frzk and curzolapierre and removed request for a team May 26, 2026 07:33
Copy link
Copy Markdown
Member

@curzolapierre curzolapierre left a comment

Choose a reason for hiding this comment

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

Questions:

  1. I noticed that the page src/_posts/languages/nodejs/2000-01-01-puppeteer.md has not been updated is that a forget or was it intentional?
  2. About src/_includes/scalingo_22_deprecation_note.md, why not invite user to upgrade to latest stack?

Overall LGTM

| [scalingo-26] | Ubuntu 26.04 | May 2031 | Supported |
| [scalingo-24] | Ubuntu 24.04 | May 2029 | Supported |
| [scalingo-22] ([EOL]) | Ubuntu 22.04 | May 2027 | Deprecated |
| scalingo-20 | Ubuntu 20.04 | April 2025 | Discontinued |
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Question (I cannot add a comment below this line), why not update example with scalingo-26 instead of scalingo-24?

Copy link
Copy Markdown
Contributor

@Frzk Frzk left a comment

Choose a reason for hiding this comment

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

unrelated-nitpick: there's a typo on the PHP page. Else LGTM!

{% endnote %}

If you do not use `compose.json` (classic app), you can specify the PHP version
If you do not use `compose.json` (classic app), you can specify the PHP version
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
If you do not use `compose.json` (classic app), you can specify the PHP version
If you do not use `composer.json` (classic app), you can specify the PHP version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants