#38: Update legacy versions

[christopher-b]

Fixes #38

• Consider v2.6 and 3.0 legacy
• Update documentation to indicate new legacy versions
• Update documentation use the most recent version in examples
• Add note to documentation regarding maintenance of version 2.7 as the default
• Update CHANGELOG

Bare minimum self-checks

What do you think of a person who only does the bare minimum?

• I've updated this PR with the latest code from main
• I've done a cursory QA pass of my code locally
• I've ensured all automated status check and tests pass
• I've connected this PR to an issue

Pieces of flare

• I've written a unit or functional test for my code
• I've updated relevant documentation it my code changes it
• I've updated this repo's README if my code changes it
• I've updated this repo's CHANGELOG with my change unless its a trivial change (like updating a typo in the docs)

Finally

• I've requested a review with relevant people

If you have any issues or need help please join the #contributors channel in the Lando slack and someone will gladly help you out!

You can also check out the coder guide.

[netlify]

👷 Deploy request for lando-ruby pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	365bbea

[christopher-b]

I'm not sure why those "should not serve port 80 for cli" tests are failing; they pass locally. Investigating.

[reynoldsalec]

We saw the same thing over on nginx, see this comment for the solution @christopher-b: lando/nginx#63 (comment)

[reynoldsalec]

Only comment I have on the code: if you can use past tense ("Updated" vs "Update") on the Changelog you'll make Pirog happy...he got me to submit on that after many harangues.

[christopher-b]

Done and done!