Update the emitter version to latest

[MaryGao]

Update the emitter version to latest

[MaryGao]

/check-enforcer override

[weshaggard]

We have been trying to avoid using tags here as they tend to break things. Is there a plan to ensure publishing a new version doesn't break existing consumers?

[qiaozha]

maybe use ^.

[MaryGao]

@weshaggard Sorry for the late response. Simply speaking, I don't think pin to any version could avoid to break existing consumers considering the emitter uses peerDependencies with range which would always fetch the latest peer dependencies.

• If these breakings are introduced from underlying dependencies for example typespec compiler, and break the emitter and finally break our end users, then upgrading to the latest emitter would work;
• If these breakings are introduced by emitter for example the supported feature surfaces change, then encuraging users to use the latest would be recommanded.

[mikeharder]

For repeatable builds, we should be pinning the versions of the packages we care about in package.json, and also checking in a package-lock.json which pins all packages. I can create PRs for these issues tomorrow, or you can:

#26197
#26198

[MaryGao]

Thanks for info, pinning all packages would make sense to me.
@mikeharder I can take these, just double confirm the emitter-package-lock.json would be treated as package-lock.json alongside package.json, Right?

PR is here: #26200

[mikeharder]

@MaryGao: See my feedback in #26200