# Deployment instructions skipped due to DPL compatibility issues

**URL:** <https://travis-ci.community/t/deployment-instructions-skipped-due-to-dpl-compatibility-issues/14664>\
**Category:** Deployment\
**Tags:** windows\
**Created:** [September 2, 2025, 4:22pm UTC](https://travis-ci.community/t/deployment-instructions-skipped-due-to-dpl-compatibility-issues/14664 "2025-09-02T16:22:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dsbaule](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/dsbaule/32/9210_2.png) [@Dsbaule](https://travis-ci.community/u/Dsbaule)\
**Post date:** [September 2, 2025, 4:22pm UTC](https://travis-ci.community/t/deployment-instructions-skipped-due-to-dpl-compatibility-issues/14664/1 "2025-09-02T16:22:25Z")

</div>

Recently, our windows builds started skipping the deployment steps with the following message:

```auto
WARNING: Skipping deployment instructions. In this OS environment version, it is not possible to use DPL v2 by default due to compatibility issues between legacy system components and the modern Ruby version. Please use the older DPL v1 instead by modifying only this specific build job recipe to include.

```

We haven’t changed anything in our build script and it was working until a while ago. Here’s our yml:

```yaml
os: windows

services:
  - docker

language: csharp
mono: none

install:
  - choco install dotnetcore-sdk
  - choco install dotnet-6.0-sdk

before_script:
  - dotnet clean
  - dotnet restore

script:
  - dotnet build
  - if [[-z ${TRAVIS_TAG}]]; then dotnet test; fi

deploy:
  provider: script
  edge:
    branch: v2.0.3-beta.4
  script: ./publish.bat $TRAVIS_TAG
  on:
    tags: true

```

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [October 14, 2025, 3:03pm UTC](https://travis-ci.community/t/deployment-instructions-skipped-due-to-dpl-compatibility-issues/14664/2 "2025-10-14T15:03:44Z")

</div>

This should be resolved now.