Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "mongo":
  In snapshot (Gemfile.lock):
    mongo (= 2.4.3)

  In Gemfile:
    mongo (= 2.4.3)

    mongoid (>= 6.2.1, <= 7.0.2) was resolved to 6.3.0, which depends on
      mongo (>= 2.5.0, < 3.0.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Bundler could not find compatible versions for gem "mongoid":
  In Gemfile:
    mongoid (>= 6.2.1, <= 7.0.2)

    kaminari-mongoid (= 1.0.1) was resolved to 1.0.1, which depends on
      mongoid

    mongoid_rails_migrations was resolved to 1.1.0, which depends on
      mongoid (>= 4.0.0)

Bundler could not find compatible versions for gem "warden-oauth2":
  In Gemfile:
    gds-sso (~> 13.6) was resolved to 13.6.0, which depends on
      warden-oauth2 (~> 0.0.1)

Could not find gem 'warden-oauth2 (~> 0.0.1)', which is required by gem 'gds-sso (~> 13.6)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Could the mainstream index on preview be regenerated from production? I'm seeing duplicate or results which 404.

https://www.preview.alphagov.co.uk/search?q=child+benifit

Examples:
/calculate-your-child-maintenance-v2
/calculate-state-pension-v2

This might be an issue that content is being indexed before it's published maybe?

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "jasmine-core":
  In snapshot (Gemfile.lock):
    jasmine-core (= 2.5.2)

  In Gemfile:
    jasmine-core (= 2.5.2)

    jasmine (>= 2.5.2, <= 3.3.0) was resolved to 2.6.0, which depends on
      jasmine-core (>= 2.6.0, < 3.0.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Bundler could not find compatible versions for gem "warden-oauth2":
  In Gemfile:
    gds-sso (~> 13.6) was resolved to 13.6.0, which depends on
      warden-oauth2 (~> 0.0.1)

Could not find gem 'warden-oauth2 (~> 0.0.1)', which is required by gem 'gds-sso (~> 13.6)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

According to the content schema, parts of a guide are optional. This would mean a guide could have no content and that seems wrong.

When I first tested this on 20 Apr, I had problems previewing content:

1. Remove a single part from a guide
2. Save
3. Try to preview

This preview failed and the draft stack told me "Page not found" I also tried the same but publishing at the end, also "Page not found".

During this time, when I removed all parts from a guide and hit save, the page told me the guide had saved successfully, and when coming back to it I could see there were no parts in the document.

Today, Apr 21, I tried this again to see if preview was working. Following the same steps I could see that removing a single part and saving, that parts was removed and I could see the draft on the draft stack.

However – when I tried to remove all parts the application responded differently. The form would not save, the inspector showed me that the POST request to remove all parts was 404ing.

The icon on the get started button is cut off on the mobile breakpoint.

Although there is a specific background-position for this breakpoint, it is is set to 110%.
I would suggest changing to something more like 104% for it to be centred inside the right hand padding.

I'm trying to get Publisher to work together with asset-manager, but having problems:

Summary:

• Publisher talks to the asset manager via the gds-api-adapters gem.
• The README for that gem states that authentication is only used for Panopticon.
• Publisher does not set any options for the asset manager API adapter in config/initializers/gds_api.rb; no bearer token, no basic auth. gds-api-adapters doesn't provide any defaults, as it does for panopticon.
• However, asset-manager responds with 401 unauthorized responses when publisher asks for things, so it's obviously expecting some auth config somewhere.

This implies that some configuration is missing, possibly being written into the app at deploy time.

Is this the case, and if so, what is it that's missing? What is asset-manager expecting to receive, and does it similarly have configuration written at deploy time for this?

The README says that These instructions are out of date. Updates coming soon

@jystewart wrote that over 2 years ago. Can we update the README with appropriate instructions please, or remove the suggestion that we will be providing updates soon?

The first error is:

Could not find bson_ext-1.4.1 in any of the sources

After a little investigation it looks like the following gems listed in Gemfile.lock have been yanked from rubygems.org. I didn't try to work out why they were yanked.

• bson 1.4.1
• bson_ext 1.4.1
• mongo 1.4.1

Finally, are we happy to use Github issues to report these sort of problems?

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "warden-oauth2":
  In Gemfile:
    gds-sso (~> 13.6) was resolved to 13.6.0, which depends on
      warden-oauth2 (~> 0.0.1)

Could not find gem 'warden-oauth2 (~> 0.0.1)', which is required by gem 'gds-sso (~> 13.6)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Hey

Is there any screenshots of the app? Any user documentation?

Dependabot can't resolve your Ruby dependencies.

As a result, Dependabot couldn't update any of your dependencies.

This could have been caused by a git reference having been deleted at the source, by an out-of-sync lockfile, or by a bug in Dependabot.

To help diagnose the issue, please try running bundle update --patch locally. If no errors occur, get in touch and we'll help dig into it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Regarding #708, when testing on integration this breaks the functionality of the selection box. It should be noted that the e2e tests and the unit tests are both showing as passing for this upgrade.

Before (other names removed from screenshot):

After:

It would be great if someone could update the README, having all these mini tools is a neat approach but without adequate documentation it's difficult for outsiders to get things up and running. Then again, I'm a bit of a noob and this Mono error is probably pretty straightforward if you're more used to MongoDB than me. Thanks!

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "mongo":
  In snapshot (Gemfile.lock):
    mongo (= 2.4.3)

  In Gemfile:
    mongo (= 2.4.3)

    mongoid (>= 6.2.1, <= 7.0.2) was resolved to 6.3.0, which depends on
      mongo (>= 2.5.0, < 3.0.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Bundler could not find compatible versions for gem "mongoid":
  In Gemfile:
    mongoid (>= 6.2.1, <= 7.0.2)

    kaminari-mongoid (= 1.0.1) was resolved to 1.0.1, which depends on
      mongoid

    mongoid_rails_migrations was resolved to 1.1.0, which depends on
      mongoid (>= 4.0.0)

Bundler could not find compatible versions for gem "warden-oauth2":
  In Gemfile:
    gds-sso (~> 13.6) was resolved to 13.6.0, which depends on
      warden-oauth2 (~> 0.0.1)

Could not find gem 'warden-oauth2 (~> 0.0.1)', which is required by gem 'gds-sso (~> 13.6)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "jasmine-core":
  In snapshot (Gemfile.lock):
    jasmine-core (= 2.5.2)

  In Gemfile:
    jasmine-core (= 2.5.2)

    jasmine (>= 2.5.2, <= 3.3.0) was resolved to 2.6.0, which depends on
      jasmine-core (>= 2.6.0, < 3.0.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Bundler could not find compatible versions for gem "warden-oauth2":
  In Gemfile:
    gds-sso (~> 13.6) was resolved to 13.6.0, which depends on
      warden-oauth2 (~> 0.0.1)

Could not find gem 'warden-oauth2 (~> 0.0.1)', which is required by gem 'gds-sso (~> 13.6)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "jasmine-core":
  In snapshot (Gemfile.lock):
    jasmine-core (= 2.5.2)

  In Gemfile:
    jasmine-core (= 2.5.2)

    jasmine (>= 2.5.2, <= 3.3.0) was resolved to 2.6.0, which depends on
      jasmine-core (>= 2.6.0, < 3.0.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Bundler could not find compatible versions for gem "warden-oauth2":
  In Gemfile:
    gds-sso (~> 13.6) was resolved to 13.6.0, which depends on
      warden-oauth2 (~> 0.0.1)

Could not find gem 'warden-oauth2 (~> 0.0.1)', which is required by gem 'gds-sso (~> 13.6)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "warden-oauth2":
  In Gemfile:
    gds-sso (~> 13.6) was resolved to 13.6.0, which depends on
      warden-oauth2 (~> 0.0.1)

Could not find gem 'warden-oauth2 (~> 0.0.1)', which is required by gem 'gds-sso (~> 13.6)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Hi Publisher team 👋

There's a few accessibility issues with the sign in pages. Example, example 2.

I'm not sure how to report (posted a message on cross gov slack), so raising here.

Issues:

1. Missing Error: in page title when in error
2. Error summary isn't focused on page load
3. Error summary is using a negative contraction
4. The markup for the radios looks like it needs review - there's a fieldset inside a fieldset.
5. I don't think the error message next to the radios is actually semantically linked in any way to the question. On the design system markup, the fieldset references the error. I can't see that happening here.

General design stuff:

1. The error styling on the radios is incomplete