Skip to content
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

chore(deps): bump fast-loops from 1.1.3 to 1.1.4 #118

Merged
merged 4 commits into from
Jul 23, 2024

Commits on Jul 10, 2024

  1. chore(deps): bump fast-loops from 1.1.3 to 1.1.4

    Bumps [fast-loops](https://github.com/robinweser/fast-loops) from 1.1.3 to 1.1.4.
    - [Commits](https://github.com/robinweser/fast-loops/commits)
    
    ---
    updated-dependencies:
    - dependency-name: fast-loops
      dependency-type: indirect
    ...
    
    Signed-off-by: dependabot[bot] <support@github.com>
    dependabot[bot] authored Jul 10, 2024
    Configuration menu
    Copy the full SHA
    110d689 View commit details
    Browse the repository at this point in the history

Commits on Jul 12, 2024

  1. release: 0.14.0 (#120)

    ### Description
    
    **Release 0.14.0** introduces support for multi-account configuration.
    With this release, admins will be able to specify multiple PagerDuty
    accounts in the same Backstage instance. Support was added across all
    the components of the plugin:
    
    - **Backend:** All API routes exposed take account as an optional
    parameter so you can create and query information from different
    PagerDuty Accounts. If admins leverage the Entity Mapping feature, the
    account is now persisted into the plugin database.
    - **Scaffolder Actions:** When the scaffolder action is used on a
    template it now lists Escalation Policies from all accounts configured
    so the user can easily select the one they want. The Scaffolder action
    also outputs the account so it can be replaced in the `app-config.yaml`
    annotations.
    - **Entity Processor:** If an entity mapping stored in the plugin
    database contains the `account` property, the processor will add an
    annotation to the entity with its information.
    
    This release solves an existing problem for many large organizations
    that have several PagerDuty accounts for segregation purposes or that
    result from company acquisitions.
    
    ## Acknowledgement
    
    By submitting this pull request, I confirm that you can use, modify,
    copy, and redistribute this contribution, under the terms of your
    choice.
    
    **Disclaimer:** We value your time and bandwidth. As such, any pull
    requests created on non-triaged issues might not be successful.
    t1agob authored Jul 12, 2024
    Configuration menu
    Copy the full SHA
    daec2a0 View commit details
    Browse the repository at this point in the history

Commits on Jul 23, 2024

  1. Configuration menu
    Copy the full SHA
    083245e View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    f107444 View commit details
    Browse the repository at this point in the history