Skip to content

v1.1.0

Marketplace
Marketplace
Compare
Choose a tag to compare
@univdev univdev released this 25 Oct 07:25
· 3 commits to master since this release
v1.1.0
3250777
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release v1.1.0 - Vercel Deploy with Slack Notification

We are thrilled to introduce v1.1.0 of the vercel-deploy-with-slack GitHub Action! This release brings added flexibility and customization for Slack notifications, allowing for a more dynamic integration with your CI/CD pipeline.

What's New:

  • Optional Slack Integration: Slack webhook inputs are now optional. If no Slack URL or payload is provided, the action can proceed without sending notifications, offering a more flexible use case for teams that may not always require Slack updates.
  • Payload File Support: You can now specify a file path for your Slack notification payloads, providing an alternative way to define custom messages outside of the workflow YAML.
    • slack-deploy-start-message-payload-file: A file containing the custom payload for the deployment start message. Overrides the inline payload if both are provided.
    • slack-deploy-failed-message-payload-file: A file containing the custom payload for the deployment failure message. Overrides the inline payload if both are provided.
    • slack-deploy-succeed-message-payload-file: A file containing the custom payload for the deployment success message. Overrides the inline payload if both are provided.
  • Backward Compatibility: Existing inputs for inline Slack message payloads (slack-deploy-start-message-payload, slack-deploy-failed-message-payload, and slack-deploy-succeed-message-payload) remain supported, ensuring compatibility with previous configurations.

Inputs:

  • vercel-token-id: Vercel API token for authenticating the deployment requests.
  • slack-webhook-url (optional): Incoming Webhook URL to send the deployment status updates to Slack.
  • slack-deploy-start-message-payload (optional): Custom payload for the deployment start message.
  • slack-deploy-failed-message-payload (optional): Custom payload for the deployment failure message.
  • slack-deploy-succeed-message-payload (optional): Custom payload for the deployment success message.
  • slack-deploy-start-message-payload-file (optional): File path for a custom payload for the deployment start message.
  • slack-deploy-failed-message-payload-file (optional): File path for a custom payload for the deployment failure message.
  • slack-deploy-succeed-message-payload-file (optional): File path for a custom payload for the deployment success message.

Outputs:

  • process-time: Total time taken to complete the deployment process.

Example Use Case:

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Deploy to Vercel and Notify Slack
        uses: univdev/[email protected]
        with:
          vercel-token-id: ${{ secrets.VERCEL_TOKEN }}
          slack-webhook-url: ${{ secrets.SLACK_WEBHOOK }}
          slack-deploy-start-message-payload-file: './slack_payloads/start.json'
          slack-deploy-failed-message-payload-file: './slack_payloads/failed.json'
          slack-deploy-succeed-message-payload-file: './slack_payloads/success.json'

This update makes it easier to manage Slack notifications and adapt them to your team's specific needs, whether by using inline messages or files for better organization. We hope these enhancements improve your deployment process and help maintain seamless communication with your team!

Assets 2
Loading