Released Documentation
HomeSupport
  • Getting started
    • Overview
    • Concepts
    • Setup Guide
      • Installing Released
      • Embedding the Widget
      • Embedding the Page
      • Implementing User Verification
      • Changelog Description Field (optional)
  • Permissions
  • Global Settings
    • General
    • Design
    • Internal Domains
    • User Verification
  • Workspace
    • Overview
    • Dashboard
    • Changelog
      • AI Settings
      • Changelog filter
      • Creating and Managing Posts
      • Writing a Post
      • Publishing Updates
      • Templates
      • Editor
        • Images
        • Videos
        • Emojis
        • Keyboard Shortcuts
        • Categories
        • Versions
      • Filter
    • Roadmaps
    • Settings
      • General
      • Access
      • Portal
        • Page Embed
        • Widget Embed
      • Publishing
        • Confluence
        • Email
        • Jira issue links
    • Integrations
      • Framer
      • Webflow
      • Slack
      • Aura
      • Cosmos
      • Karma
      • Scroll Viewport for Confluence
  • Resources
    • AI Tips
      • Create Output in Other Languages
      • Include a Documentation Link in the Output
      • Creating Structured Output
    • Troubleshooting
      • Permissions Issues
    • How-Tos
      • Accessing Custom Fields
      • Configuring Dark Mode
      • Finding the Channel ID
      • Ensuring JavaScript Resource Stability for PCI Compliance
      • How to Open the developer console to check for errors
      • How to Apply Atlassian Marketplace App Promo Codes for Cloud
      • Configuring Content Security Policies (CSP) for Released Embeds
Powered by GitBook
On this page
  • Understanding the Current Setup
  • Directly Referencing the Hashed File
  • Benefits of Direct Reference
  • Considerations
  • Future Versioning

Was this helpful?

  1. Resources
  2. How-Tos

Ensuring JavaScript Resource Stability for PCI Compliance

How can I ensure that the referenced JavaScript resource doesn't change for PCI compliance reasons?

PreviousFinding the Channel IDNextHow to Open the developer console to check for errors

Last updated 11 months ago

Was this helpful?

To ensure that the referenced JavaScript resource remains stable and doesn't change unexpectedly, follow these steps:

Understanding the Current Setup

  • We currently provide a loader file that dynamically references the latest hashed version of the embed code. You can access the loader file here: .

  • When you load this loader file in the browser, it redirects you to the latest hashed version of the embed code, such as .

Directly Referencing the Hashed File

Instead of using the loader file, you can directly reference the hashed file. This ensures that the file will not change, thus maintaining PCI compliance. For example, use the URL provided by the loader file (e.g., ).

Benefits of Direct Reference

  • Stability: The file content remains consistent and unchanged, preventing unexpected issues.

  • Compliance: Helps maintain PCI compliance by using a stable, verified file.

Considerations

Manual Updates: By referencing the hashed file directly, you will not automatically receive updates or improvements. You will need to manually update to the latest version when it becomes available.

Future Versioning

We have not made any breaking changes to the file to date. Before implementing any such changes, we will introduce proper versioning to ensure seamless updates.

https://embed.released.so/1/embed.js
https://embed.released.so/CeAQG3QB/embed.js
https://embed.released.so/CeAQG3QB/embed.js