Dev-env

Latest version: v0.6.21

Safety actively analyzes 630360 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 10 of 13

0.5.20

Added

* cfg4dev now installs [increment_version.sh](https://github.com/fmahnke/shell-semver) in the bin directory
so that development of python-increment-version.sh is possible
* add support for .shellcheckignore so run-shellcheck.sh can ignore
specific files

Changed

* fixed bug in run-unit-tests.sh which wasn't looking for .coveragerc in the repo root directory
* run-shellcheck.sh sorts shell scripts before scanning
* python-increment-version.sh now accepts command line arguments of M, m and p
instead of -M, -m and -p

Removed

* Nothing

0.5.19

Added

* created bin/in-container/should-be-the-same.sh and called it from the CI pipeline to ensure
scripts on bin and bin/in-container that are supposed to be the same really are the same

Changed

* bin/check-consistent-dev-env-version.sh and bin/in-container/check-consistent-dev-env-version.sh are now the same

Removed

* Nothing

0.5.18

Added

* add --verbose command line option to check-consistent-dev-env-version.sh

Changed

* Nothing

Removed

* Nothing

0.5.17

Added

* Nothing

Changed

* fixed bug in check-consistent-dev-env-version.sh when normalizing of version numbers
* mock 2.0.0 -> 3.0.5

Removed

* requirements.txt in the repo's root directory since it's no longer used

0.5.16

Added

* [Bandit (a tool designed to find common security issues in Python code)](https://github.com/PyCQA/bandit)
is now available in the dev-env docker image
* added check-consistent-dev-env-version.sh to detect dev-env version drift
* install-dev-env.sh is now the recommended way for dev-env to be installed by a cfg4dev script
* added python-increment-version.sh for use in .cut-release-master-branch-changes.sh
* cut-release.sh now creates a github release

Changed

* bin/in_container directory renamed to bin/in-container - should affect no one
* run-unit-tests.sh now pulls the html coverage reports from inside
* renamed prep-for-release.sh -> cut-release.sh

Removed

* removed prep-for-release-python.sh and replaced with cut-release.sh which is a far more generalizable version of prep-for-release.sh
* removed dev-env-nosetests.py since it no longer seemed to be used

0.5.15

Added

* added current-python-version.sh which is used to extract a python project's version number
* added changelog-dot-md-release-comments.py which is used to extract the notes for a single release from CHANGELOG.md
* added snyk, nvm, node, markdownlint-cli, jq, git, docker-ce and shellcheck to Ubuntu Xenial docker image
* added run-snyc.sh to simplify running [snyc](https://snyk.io/) CLI against a repo
* added -u command line option to repo.sh to convert dashes in repo's name to underscores
* added upload-dist-to-pypi.sh (both in container and on host) to publish Python packages on pypi using [twine](https://pypi.org/project/twine/)
* added get-dev-env-version-from-circleci-config.sh
* added run-yamllint.sh to make it easy to run [yamllint](https://yamllint.readthedocs.io)
* added run-circleci.sh to simplify running the [CircleCI](https://circleci.com) [CLI](https://circleci.com/docs/2.0/local-cli/) inside a dev env container

Changed

* flake8 3.7.4 -> 3.7.7
* twine 1.12.1 -> 1.13.0
* fixed bug in run_shellcheck.sh where docker containers weren't being removed are they had exited
* using "$(echo "${1:-}" | tr "[:upper:]" "[:lower:]")" instead of "${1,,}" and [[:space:]] instead of \s with sed so scripts work on macOS and Ubuntu
* prep-for-release.sh now uses cut-changelog-dot-md.py and add-new-changelog-dot-md-release.py to improve portability across macOS and Ubuntu as well as simplifying prep-for-release.sh

Removed

* no longer need to set DEV_ENV_PACKAGE and DEV_ENV_SOURCE_CODE

Page 10 of 13

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.