-
Notifications
You must be signed in to change notification settings - Fork 31
Prepare for next release #892
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…avoid the use of weak encryption algorithms
Co-authored-by: mjain6 <mjain6@opentext.com>
…irectly (#868) Co-authored-by: mjain6 <mjain6@opentext.com>
…pped during audit (#882) fix: `fcli aviator`: Correct filtering logic to prevent valid issues from being skipped during audit fix: `fcli aviator`: Ensure consistent file hash generation across different builds Co-authored-by: cdatla <cdatla@opentext.com>
fix: `fcli ssc session login`: Fail with proper error if supplied token is invalid Co-authored-by: mjain6 <mjain6@opentext.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: rsenden <8635138+rsenden@users.noreply.github.com>
fix: `fcli fod sast-scan setup`: Keep existing settings for "aviator" and "oss" unless explicit `--[no-]oss` or `--[no-]use-aviator` specified (fixes #885) Co-authored-by: kadraman <klee2@opentext.com>
feat: `fcli tool definitions update`: Add `--max-age` option to only update definitions if older than specified period (e.g., `1h`, `4h`, `1d`) feat: `fcli tool definitions update`: Add `--force` option to update definitions even if they are up-to-date feat: `fcli tool * register`: New commands for registering existing tool installations with automatic version detection (supports binary path, bin directory, or installation directory) feat: `fcli tool * get`: New commands for displaying detailed information about a specific installed tool version feat: `fcli tool env init`: New command for automatically setting up one or more Fortify tools (auto-detects pre-installed tools, downloads if necessary, supports air-gapped environments, and platform-specific tool caching) feat: `fcli tool env shell|powershell|github|gitlab|ado|expr`: New commands for generating environment variable exports for installed or registered tools in various shell or CI/CD-specific formats feat: `fcli tool * install`: Tool installations now show action status (installed/copied/registered/skipped) for better visibility feat: `fcli tool * install`: Add hidden `--copy-if-matching` option (internal use by `fcli tool env init`) to copy from existing installation instead of downloading feat: `fcli tool sc-client install`: Add `--jre` option to specify custom JRE home directory for use with `fcli tool sc-client run` command feat: `fcli tool sc-client install`: Improve JRE handling with automatic detection from environment variables (`SC_CLIENT_JRE_HOME`, `SCANCENTRAL_JRE_HOME`) chore: `fcli tool * install`: Remove deprecation warning for `--install-dir` option feat: fcli `ci` action: Add support for pre-installed tools via `SC_CLIENT_HOME` and `DEBRICKED_HOME` environment variables, complementing existing dynamic installation feat: fcli `ci` action: Add support for `PREINSTALLED` environment variable to require all tools to be pre-installed, preventing automatic downloads fix: fcli `ci` action: Post-scan tasks (check-policy, release-summary, pr-comment, export) are now properly skipped if no scans were run feat: fcli `detect-env` action: Renamed from `ci-vars` and updated to provide general environment detection capabilities (CI platform, Git repository, ...) feat: fcli `package` action: Simplify tool setup by using `fcli tool env init` instead of separate update/install steps feat: fcli `package` action: Change default `--sc-client-version` from `latest` to `auto` for smarter version resolution feat: fcli `debricked-scan` action: Simplify tool setup by using `fcli tool env init` instead of separate update/install steps feat: fcli `debricked-scan` action: Change default `--cli-version` from `latest` to `auto` for smarter version resolution feat: Action SpEL functions: Add `#opt(name, value)` function for conditionally formatting command-line options chore: `fcli action run ci`: Remove "PREVIEW" labels - now considered production-ready chore: `fcli action run package`: Remove "PREVIEW" label - now considered production-ready chore: Various fcli actions: Improve command-line argument quoting for better shell compatibility (use `"--option=value"` format) fix: Improve error handling and error output chore: Add `--skip-if-exists` and `--auto-required-attrs` options as reusable mixins for FoD and SSC create commands chore: FileUtils: Add new glob pattern matching methods (`processMatchingFileStream`, `processMatchingDirStream`, `processMatchingStream`) with support for Ant-style patterns chore: Add `JreHelper` utility class for JRE-related operations chore: Improve exception handling by using `FcliSimpleException` instead of generic exceptions in DateTimePeriodHelper and FcliVariableHelper chore: Hide generic fcli options (`--help`, `--env-prefix`) from wrapper tool help output like `@fortify/setup` docs: Add comprehensive Developer Integration Guide (`developer-integration-guide.md`) for CI/CD platform integrations docs: Document fcli bootstrap strategy and semantic versioning support for platform integration tools docs: Document `--self` parameter for `fcli tool env init` to enable efficient tool copying from bootstrapped fcli chore: Add FileUtils glob pattern matching tests chore: Add functional tests for tool register commands ci: Add concurrency control to cancel redundant workflow runs ci: Improve pull request handling in functional test triggering ci: Fix branch name handling for development releases ci: Prevent duplicate workflow runs on push to PR branch
feat: Add UBI9 images for fortifydocker/fcli
fix: fcli `debricked-scan` action: Show Debricked output both on successful run and in case of errors fix: fcli `debricked-scan` action: Mask Debricked token in console output chore: Extend log masking capabilities to console output
This reverts commit bc52260.
feat: Add fcli state persistency information in help output and 'session not found' errors when running in Docker containers feat: Publish shell-based UBI9 variant of fortifydocker/fcli to allow for interactive use
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.