Use the latest satellite version

[DukeManh]

This changes the Satellite version from 1.17 to 1.x. We manage Satellite ourselves so it's safe to not pin it and let ppm install the latest minor/patch if any.

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[gitpod-io]

[humphd]

Looks good. I was going to say you missed the autodeployment server, but it already does this

telescope/tools/autodeployment/package.json

Line 8 in 5397a02

"@senecacdot/satellite": "^1.x",

[DukeManh]

Just rebased.

but it already does this

Did Renovate miss this when it was pinning dependencies?

[humphd]

Not sure, I wonder if it did.

[TueeNguyen]

1 question, satellite in src/package.json will be pinned to 1.17 when my #2615 gets merged? And then we're gonna change it to 1.x right?

[DukeManh]

Yeah, It depends on which one gets merged first. It'll be best that you also use ^1.x in your PR so there are no conflicts.
Remember to run pnpm install after the change.

[TueeNguyen]

Yup, I'll change it to 1.x for less work.

[DukeManh]

Renovate doesn't like autodeployment, no dependencies were pinned there.

https://github.com/Seneca-CDOT/telescope/blob/4fa446171c1ee30b0ddab49961efcb6adafe1f81/tools/autodeployment/package.json