Note: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
distro attribute in the package.json with the commit ID of the distro repo.i18n folder git history for latest translations, then build locally and see the amount of untranslated strings) @dbaeumerv1_21.md in this repo directory. This includes new features and notable fixes.insider builds - endgame masterrelease/<x.y> and release master - endgame masterpackage.json - endgame masterrelease/<x.y> change authorInsider from release/<x.y> endgame masterInsider endgame masterHEAD of release/<x.y> in format x.y.z endgame masterinsider builds endgame masterIt's quite frustrating that vscode installed by rpm through the repo is notifying me of an update when it isn't available in the repo.
Perhaps code installed this way shouldn't show update notifications and leave that to the package manager (alternately speed up the upload process)
Publish deb and rpms to repositories manually
A week after release and I still don't have the Feb build available via rpm. Can this be automated for the future? Could we get the current one up there?
@lynchem we're having issues with the internal service used to publish the rpm and are working with the team that owns that to resolve it. Automating this would be a huge weight off my shoulders every month but it's not currently possible.
@Tyriar understand it can be hard but the 'an update is available' notification every time a window is opened gets frustrating, especially when I actually want to update
@ZanderBrown see https://github.com/Microsoft/vscode/issues/43671
Most helpful comment
@lynchem we're having issues with the internal service used to publish the rpm and are working with the team that owns that to resolve it. Automating this would be a huge weight off my shoulders every month but it's not currently possible.