Draft
Conversation
- Introduced multiple GitHub Actions workflows for the Go project, including: - `go-attach-to-release.yml`: Attaches built assets to GitHub releases. - `go-build.yml`: Cross-compiles the Go application for various platforms. - `go-docker.yml`: Builds and tests Docker images for the application. - `go-main.yml`: Orchestrates the main CI process, including testing, building, and packaging. - `go-process-assets.yml`: Processes and packages build artifacts. - `go-test-install-post-build.yml`: Tests the installation of the application on various Linux distributions. - `go-test.yml`: Runs tests and vetting for the Go code. - `go-version.yml`: Extracts and validates the version from the Go source code. These workflows enhance the CI/CD pipeline, ensuring robust testing and deployment processes for the Go application.
- Introduced a new .dockerignore file to exclude unnecessary files and directories from the Docker build context, improving build efficiency and reducing image size. The file includes common exclusions such as .git, .venv, __pycache__, and various build artifacts.
- Introduced a multi-stage Dockerfile to build the Go application, separating the build and runtime environments. - Added a builder stage using the Go image to compile the application, including necessary dependencies and build arguments. - Updated the runtime stage to use a minimal Alpine image, ensuring a lightweight final image with only the compiled binary and CA certificates. - Enhanced the build process with a patch replace directive for the Go module, improving dependency management.
- Added new files for managing the MCP server and client configurations, including installation and uninstallation of server settings for various clients. - Introduced safety checks for command execution and output sanitization to enhance security. - Implemented functions for detecting installed clients and managing secret values securely. - Established a structured approach for handling sensitive keys and validating command safety, ensuring compliance with security best practices.
Deploying phase-cli-install-script with
|
| Latest commit: |
a7b6073
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4bd2ada8.phase-cli-install-script.pages.dev |
| Branch Preview URL: | https://feat--cli-2-0.phase-cli-install-script.pages.dev |
… Auth, and Init functions
…rove client initialization
…reamline environment variable handling
…d simplifying key-value pair handling
…action and utilizing phase methods
…andling and leveraging phase methods
… data handling and utilizing phase methods
…og warining to sderr
…error handling - Replace ambiguous-width emoji (🏷️→🔖, ⛓️→🌐) with consistently 2-column alternatives to fix table border misalignment across terminals - Extract shared runeWidth() helper for DRY width calculation - Add full-width terminal table rendering with value wrapping - Restore secret injection stats output to stderr in run command - Add dynamic secret lease support to secrets list command - Add structured SDK error formatting in CLI error layer
- Remove all legacy Python CI workflows (pytest, pypi, process-assets, etc.) - Rename Go workflows to drop go- prefix (go-build.yml → build.yml, etc.) - Add FPM packaging step: scripts/package.sh produces .deb, .rpm, .apk for amd64 + arm64 (6 packages total) - Add package.yml workflow to run FPM in CI after build - Enhance test-install-post-build.yml to test package installs (dpkg -i, rpm -i, apk add) not just raw binary copies - Add test-install-script.yml for post-release install.sh e2e testing - Enhance install.sh cleanup_legacy() with user consent prompt, --no-cleanup flag, and /usr/bin/_internal cleanup - Add scripts/test-migration.sh for local Docker-based migration testing
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.