Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(maint) Finish the 2.4.0 release by merging master to develop #3562

Merged
merged 13 commits into from
Nov 13, 2024
Merged

Conversation

vexx32
Copy link
Member

@vexx32 vexx32 commented Nov 13, 2024

Description Of Changes

Back-merging changes from master to develop.

Motivation and Context

Finishing out the 2.4.0 release.

Testing

N/A

Operating Systems Testing

N/A

Change Types Made

  • Bug fix (non-breaking change).
  • Feature / Enhancement (non-breaking change).
  • Breaking change (fix or feature that could cause existing functionality to change).
  • Documentation changes.
  • PowerShell code changes.

Change Checklist

  • Requires a change to the documentation.
  • Documentation has been updated.
  • Tests to cover my changes, have been added.
  • All new and existing tests passed?
  • PowerShell code changes: PowerShell v3 compatibility checked?

Related Issue

N/A

corbob and others added 13 commits June 10, 2024 08:06
The MSI was erroneously creating the C:\ProgramData\Chocolatey
directory. This caused the install script to fail silently and not
actually install Chocolatey. This removes the directory from the install
and just lets the install script install to the default location.
The MSI was generating a C:\Tools directory, but never actually using
it. This commit removes the Tools directory from the install so it is
never created.
Since these files are not copied to the output folder, and instead
are added to the choco.exe as resources, we need to additional verify
each script file from the source location, in the same way that they
are selected when they are being signed.
This is an attempt to ensure that any changes to our dependencies,
whether that is:

* changes to NuGet packages through packages.config files
* updates to custom assemblies which are not tracked through NuGet
packages
* updates to custom executables/assemblies which are added directly to
the Chocolatey CLI Chocolatey Packages

Are trakced and updated properly.  By making these files/folder owned
by the new @chocolatey-credits-reviewers group, it means that a member
of that group will be flagged on any PR's that we raised that contain
these files.
This updates the tests to validate that the version number is not
output in the Info log messages only. There are some debug log messages
that may contain a similar version number as they report the user agent
being used, this prevents them from being erroneously picked up.
The debug log is used in a lot of places when we don't want the user to
see the output, but we want it available. At the moment it is not
consistent about what we do when they select debug and limit output. It
has been decided at the moment to remove these tests as they are now
breaking by us emitting the user agent to the debug log. A follow up
issue #3555 has been created to determine what we want for behaviour
when limit output and debug is selected.
Update the MSI build configuration to only build the MSI instead of
building unnecessary projects.
(maint) Remove chocolatey.benchmark and chocolatey.powershell from MSI build
Licensed does queries in the background before / while normal commands
are running, so we can end up with multiple user-agent debug lines.

Resolve this by just looking at the most recently-outputted user agent,
as these should all look the same (and if not, the last one should be
the one from the actual command run).
Automatic update from the current latest docs in the docs repo.
@vexx32 vexx32 requested a review from gep13 November 13, 2024 15:40
Copy link
Member

@gep13 gep13 left a comment

Choose a reason for hiding this comment

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

LGTM!

@gep13 gep13 merged commit 5b5b54a into develop Nov 13, 2024
12 of 13 checks passed
@gep13
Copy link
Member

gep13 commented Nov 13, 2024

@vexx32 thanks for getting this done!

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