v0.21.7

v0.21.7 (2024-01-18)

Fix

• fix: Revert "chore: pip: Bump coverage from 7.3.1 to 7.4.0 (#351)" (#378)

This reverts commit 07d696b.

Not sure if this PR might have broken our build. (fe7a27c)

v0.21.6

v0.21.6 (2024-01-18)

Chore

• chore: pip: Bump coverage from 7.3.1 to 7.4.0 (#351)

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Tyler D <[email protected]> (07d696b)

Fix

• fix: Restrict to python 3.11 & lower in pyproject.toml (#377)

By restricting the supported python range, we can fix poetry shell && poetry install to not attempt to install secureli on python 3.12.

I'm also hoping that once this gets released it will update the PyPI
listing to not include python 3.12
in the supported python versions.

I also moved up the [build-system] block to the top of
pyproject.toml, since it's a top-level & required section.

Testing

% poetry env use 3.12
Using virtualenv: /Users/tyler.durkota/Library/Caches/pypoetry/virtualenvs/secureli-TKSW7H2l-py3.12
% poetry shell

Current Python version (3.12.1) is not allowed by the project (>= 3.9, < 3.12).
Please change python executable via the "env use" command.
``` ([`3a384a4`](https://github.com/slalombuild/secureli/commit/3a384a486b85c1aa319fd8515979ba82265d69f8))

v0.21.5

v0.21.5 (2024-01-16)

Fix

• fix: Fix failing macos homebrew integration test (#371)

closes #370
updates and splits up init/scan secureli commands for homebrew mac os
integration test. The test is currently failing due to the scan command
not checking all files and expecting committed files. (ddd55a3)

v0.21.4

v0.21.4 (2024-01-16)

Fix

• fix: remove cfgv from homebrew exclude list (#369)

closes #368

remove cfgv from exclude list so that it is added to homebrew formula (abcf8c4)

v0.21.3

v0.21.3 (2024-01-16)

Documentation

• docs: Update documentation to describe release prefixes (#367)

Minor update to documentation to as a follow-up to #366

Screenshot:
<img width="768" alt="Screenshot 2024-01-16 104221"
src="https://github.com/slalombuild/secureli/assets/1209260/d1e7a10a-22ac-42c9-9ab0-65fd97e33feb&#34;> (ae16223)

Fix

• fix: Fix integration tests action (#364)

Description

Attempting to fix our Integration Tests GH action (which is really
post-release smoke testing)

There are 3 failing jobs:

1. pulling from PyPI on Windows
   a. This was failing because the scan returns a nonzero exit code. For
   now, i told the script to expect a nonzero exit code.
   b. In the future, we should have a "happy path" test case where no
   issues are found, so we can validate a success (zero) exit code.
   c. Additionally, we should use different exit codes to differentiate
   between failures because of flagged issues versus internal errors. For
   now, I have updated seCureLI to return a 3 when it flags issues, but
   I'm not explicitly checking for that error here.
2. pulling from PyPI on MacOS
   a. This was failing due to using python 3.12 in the default runner. I
   fixed it by installing & using python 3.11 on the runner.
   b. We can't yet support python 3.12 because one of our dependencies
   doesn't yet support it. If we need it in a pinch, I've included
   commented-out code for pointing to the PR branch that enables this
   support.
3. pulling from homebrew on MacOS
   a. This is failing because of our homebrew formula has an incorrect list
   of dependencies. It will need to be fixed in a future PR.

Testing

This execution shows tests passing (except for homebrew): https://github.com/slalombuild/secureli/actions/runs/7535989887

This closes #357 (0235ed1)

v0.21.2

v0.21.2 (2024-01-16)

Chore

• chore: replace unsupported google eslint with eslint recommended (#356)

closes #337

• Replace the eslint-google-config settings with eslint:recommended
  for generated typescript and javascript eslint config files.

• Add missing module identify to homebrew formula

• Fix lint config issues

  1. Fix mismatched file names in pre-commit file and config files
  2. Create separate files for JavaScript and TypeScript
  3. Add missing dependency for needed TypeScript pre-commit file (f86b5d3)

Fix

• fix: Update semantic-release config (#366)

Our current configuration for
semantic-release
seemingly indicates that "chore" PRs result in a patch release, but in
practice they do not. I've opted to update the configuration to match
the current behavior, rather than the other way around. (8b1beb3)

v0.21.1

v0.21.1 (2024-01-10)

Fix

• fix: remove pre-commit from homebrew formula ignore list (#355)

close #354 (38e0d84)

v0.21.0

v0.21.0 (2024-01-09)

Feature

• feat: Handle additional installation for newly detected languages (#346)

closes #187

During either a scan or install, users will be prompted to install any
newly detected languages:
<img width="678" alt="Screenshot 2023-12-19 at 3 50 39 PM"
src="https://github.com/slalombuild/secureli/assets/58826693/9f20b56f-8ae2-4367-8ef0-db4246bea647&#34;>

If the user cancels the additional language install or an error occurs
during language detection, the process will continue for the existing
installed languages with a warning:

<img width="747" alt="Screenshot 2023-12-19 at 4 49 11 PM"
src="https://github.com/slalombuild/secureli/assets/58826693/12feaa9a-6899-4103-b299-3e0d945351c9&#34;> (4004bcc)

v0.20.0

v0.20.0 (2024-01-09)

Feature

• feat: Only publish metrics on commit (#353)

Instead of only detecting scan vs commit scenarios, I added a CLI param
to set when metrics should be published (always, never, or
on-fail) and utilized that by setting the git pre-commit hook to
secureli scan --publish-results=always.

One other notable change is that I added a models/ directory. I think
it would make sense to migrate various pydantic models & enums there in
the future. (2cdd033)

v0.19.1

v0.19.1 (2024-01-05)

Fix

• fix: linter config file creation (#349)

closes #344

Fixes issue where linter config files (i.e. .eslintrc.yaml) were not
being created and also had generic file names. Files will now be created
using the filename and config data contents specified in the specific
yaml resources. (a59fa0b)