Update Certifier-Show branch

.gitattributes

@@ -1,6 +1,5 @@
 # linguist gets confused by PIR files, and thinks they make up a lot of our source!
 *.pir linguist-detectable=false
-stubs/plutus-ghc-stub/** linguist-vendored=true
 # Large HTML files inside 'notes' are dominating our repoistory language
 # estimate.
 notes/**/*.html linguist-documentation

.github/workflows/docusaurus-site.yml

@@ -1,4 +1,5 @@
-# This workflow builds and publishes the Docusaurus site to:
+# This workflow builds the Docusaurus site on pull_request.
+# It also publishes the site on push to master to:
 # https://plutus.cardano.intersectmbo.org/docs
 
 name: "🦕 Docusaurus Site" 
@@ -8,10 +9,11 @@ on:
     branches: 
       - master 
   workflow_dispatch:
+  pull_request:
 
 jobs:
-  deploy:
-    name: Deploy 
+  run:
+    name: Run 
     runs-on: [self-hosted, plutus-shared]
     permissions:
       contents: write
@@ -26,8 +28,9 @@ jobs:
         run: nix develop --no-warn-dirty --accept-flake-config --command bash -c 'yarn && yarn build'
 
       - name: Deploy Site 
-        uses: JamesIves/[email protected]
+        if: github.event_name == 'push'
+        uses: JamesIves/[email protected]
         with:
           folder: doc/docusaurus/build
           target-folder: docs
-          single-commit: true
+          single-commit: true

.github/workflows/haddock-site.yml

@@ -62,15 +62,15 @@ jobs:
           nix develop --no-warn-dirty --accept-flake-config --command ./scripts/combined-haddock.sh _haddock all
 
       - name: Deploy Site
-        uses: JamesIves/[email protected].3
+        uses: JamesIves/[email protected].4
         with:
           folder: _haddock
           target-folder: haddock/${{ inputs.destination || github.ref_name }}
           single-commit: true
 
       - name: Deploy Site (latest)
         if: ${{ inputs.latest == true }}
-        uses: JamesIves/[email protected].3
+        uses: JamesIves/[email protected].4
         with:
           folder: _haddock
           target-folder: haddock/latest

.github/workflows/metatheory-site.yml

@@ -59,15 +59,15 @@ jobs:
           cp -RL result/* _metatheory
 
       - name: Deploy Site
-        uses: JamesIves/[email protected].3
+        uses: JamesIves/[email protected].4
         with:
           folder: _metatheory
           target-folder: metatheory/${{ inputs.destination || github.ref_name }}
           single-commit: true
 
       - name: Deploy Site (latest)
         if: ${{ inputs.latest == true }}
-        uses: JamesIves/[email protected].3
+        uses: JamesIves/[email protected].4
         with:
           folder: _metatheory
           target-folder: metatheory/latest

.github/workflows/papers-and-specs.yml

@@ -40,7 +40,7 @@ jobs:
           done 
 
       - name: Publish Papers
-        uses: JamesIves/[email protected].3
+        uses: JamesIves/[email protected].4
         with:
           folder: _resources
           target-folder: resources

.github/workflows/plutus-tx-template.yml

@@ -1,7 +1,7 @@
-# This workflows ensures that the plutus-tx-template repository stays working 
-# even if there are changes in plutus. It checks out both the current commit of 
-# plutus and the master branch of plutus-tx-template. Then, it creates a 
-# cabal.project.local for plutus-tx-template that adjusts the plutus version. 
+# This workflows ensures that the plutus-tx-template repository stays working
+# even if there are changes in plutus. It checks out both the current commit of
+# plutus and the master branch of plutus-tx-template. Then, it creates a
+# cabal.project.local for plutus-tx-template that adjusts the plutus version.
 # Finally, it double-checks that everything still builds correctly using cabal
 # inside the devx shell.
 
@@ -17,40 +17,40 @@ jobs:
     steps:
       - name: Checkout plutus-tx-template Repo
         uses: actions/checkout@main
-        with: 
+        with:
           repository: IntersectMBO/plutus-tx-template
-          path: plutus-tx-template 
+          path: plutus-tx-template
 
       - name: Checkout plutus Repo
         uses: actions/checkout@main
-        with: 
+        with:
           path: plutus-tx-template/plutus
-  
+
       - name: Overwrite cabal.project.local
         uses: DamianReeves/write-file-action@master
         with:
           path: plutus-tx-template/cabal.project.local
           write-mode: overwrite
           contents: |
-            packages: 
+            packages:
               plutus/plutus-tx
               plutus/plutus-tx-plugin
               plutus/plutus-core
               plutus/plutus-ledger-api
               plutus/prettyprinter-configurable
-            
+
             allow-newer:
                 plutus-tx
               , plutus-tx-plugin
               , plutus-core
-              , plutus-ledger-api 
+              , plutus-ledger-api
               , prettyprinter-configurable
-          
+
       - name: Build Project With Docker
         run: |
-          cd plutus-tx-template 
+          cd plutus-tx-template
           docker run \
             -v ./.:/workspaces/plutus-tx-template \
             -w /workspaces/plutus-tx-template \
             -i ghcr.io/input-output-hk/devx-devcontainer:x86_64-linux.ghc96-iog \
-            bash -ic "cabal update && cabal run plutus-tx-template && test -e validator.uplc"
+            bash -ic "cabal update && cabal build all"

.github/workflows/slack-message-broker.yml

@@ -50,7 +50,7 @@ jobs:
             core.setOutput("message", message); 
 
       - name: Notify Slack
-        uses: slackapi/slack-github-action@v1.26.0
+        uses: slackapi/slack-github-action@v1.27.0
         env:
             SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }} 
         with:

.github/workflows/sprint-issues-rollover.yml

@@ -21,6 +21,6 @@ jobs:
         number: 18 # Find this number by looking at the project's page URL
         token: ${{ secrets.PLUTUS_BACKLOG_AUTOMATION }} # Needs project write permissions
         iteration-field: Sprint
-        iteration: last
-        new-iteration: current
+        iteration: current
+        new-iteration: next
         excluded-statuses: ❌ - won't do,🚀 - done

CHANGELOG.md

@@ -0,0 +1,9 @@
+# Plutus Changelog 
+
+Changelogs are available for these packages:
+
+- [plutus-ledger-api](./plutus-ledger-api/CHANGELOG.md)
+- [plutus-tx](./plutus-tx/CHANGELOG.md)
+- [plutus-tx-plugin](./plutus-tx-plugin/CHANGELOG.md)
+- [plutus-core](./plutus-core/CHANGELOG.md)
+- [plutus-executables](./plutus-executables/CHANGELOG.md)

CODEOWNERS.md

@@ -0,0 +1,18 @@
+# Plutus Codeowners
+
+/nix/  @zeme-wana
+/.github/workflows/  @zeme-wana
+/scripts/  @zeme-wana
+flake.nix  @zeme-wana
+flake.lock  @zeme-wana
+
+/plutus-tx/src/PlutusTx/Blueprint/  @Unisay
+/plutus-metatheory/  @ramsay-t
+/plutus-ledger-api/  @bezirg @Unisay
+/cardano-constitution/  @bezirg
+/plutus-benchmark/  @kwxm
+/plutus-conformance/  @kwxm
+/plutus-executables/  @kwxm
+/plutus-core/  @kwxm @effectfully
+/doc/plutus-core-spec/  @kwxm
+/prettyprint-configurable/ @effectfully

CODE_OF_CONDUCT.md

@@ -1 +1,132 @@
-See https://github.com/input-output-hk/cardano-engineering-handbook/blob/main/CODE-OF-CONDUCT.md
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[[email protected]](mailto:[email protected]).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

DESCRIPTION.md

@@ -0,0 +1,6 @@
+# Plutus Core 
+
+This repository hosts Plutus Core, the scripting language embedded in the Cardano ledger, which forms the basis of the Plutus Platform, an application development platform for developing distributed applications using the Cardano blockchain.
+
+For more information please refer to the [README](./README.adoc).
+