[API] Update subgraph version to include UpdatedExpiration event

[psparacino]

Description

The listings issue described below appears to be a casing issue in the frontend.

This updates the subgraph (current version breaks on activities query as there are null projects for some entities due to an uncaught case) to handle expiration date only updates.

Related Ticket

Related to #2243

How to Test

1. got to https://carbonmark-git-tufnel-fix-listings-not-showing-klimadao.vercel.app/users/jabby
2. confirm expired listings are there

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
carbon	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2024 0:25am
carbonmark	✅ Ready (Inspect)	Visit Preview		Feb 13, 2024 0:25am
carbonmark-api	✅ Ready (Inspect)	Visit Preview		Feb 13, 2024 0:25am
demo-integration	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2024 0:25am
klimadao-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2024 0:25am

[jabby09]

@psparacino expired listings are now showing

listings will show for 90 days after they expire

Don't totally understand this.
Do you mean they will show as expired listing on my Profile page?
Why only for 90 days and what happens after that?

[jabby09]

@psparacino while expired listings are showing still something not quite right

If I Edit an expired listing, it looks like the expiration date is being reset to 90 days from current date, so in this case to 5/7/2024

However, if I don't change anything else and just UPDATE LISTING it kicks off the SUBMIT process and I have to do a MM wallet confirm.

But then I just get spinning "Updating your data..." the the update does not work.

Get this error:

and listing is still showing as expired

[0xemc]

@psparacino @biwano

I'm not sure this fixes the issue. My understanding is that the user should always see their own expired listings even after 90 days.

Can we not just provide a large value for expiresAfter on the call to the api from the consumer (app)

[jabby09]

@psparacino @biwano

I'm not sure this fixes the issue. My understanding is that the user should always see their own expired listings even after 90 days.

Can we not just provide a large value for expiresAfter on the call to the api from the consumer (app)

@0xemc correct this is not completely fixed, Peter is working on it https://discord.com/channels/1135827610434289727/1204433909060730900/1204862568926281848

[0xemc]

@jabby09 @0xtapi can we give this PR the greenlight?

[jabby09]

@jabby09 @0xtapi can we give this PR the greenlight?

hey @0xemc I believe this is working now but I'm doing some final FE testing on this PR #2255

[psparacino]

@jabby09 The reverting calls on those expired listing occurred because those listings had actually already been deleted by the contract due to having less than the minimum fill amount. There was no event emitted so the subgraph didn't pick it up. The issue was fixed and new events emitted to update the subgraph so that should be separate from this issue

[0xemc]

Closing after ticks from all parties